...
Auth Mechanism | Specify the authorization mechanism you want to use to connect to the gRPC server. Options are Default is |
|---|---|
Trust Certificate File | Specify the path to a certificate file in PEM format that identifies the gRPC server. This is required for gRPC servers with self-signed certificates. Leave this field blank to use the system trust store for gRPC servers with a public certificate from a root authority. This field is ignored when the Auth Mechanism is set to |
Client Certificate Chain File | Specify the path to a PEM-formatted certificate file that provides the certificate chain. This will be combined with the Client Private Key to provide the client's identity. |
Client Private Key | Specify the client's private key in PKCS#8 format. The key can be encrypted, see Client Private Key Password. This will be combined with the Client Certificate Chain File to provide the client's identity. |
Client Private Key Password | If the client's private key is encrypted, specify its password. If the private key is not encrypted, leave this field blank. |
Call Settings
| Scroll Table Layout | ||
|---|---|---|
|
...
Multiple messaging clients (or ProtoBuf clients) are needed to test the other three gRPC method types for streaming. In each case the client requests and server responses are decoupled. Tools that are configured to send will not have any response payload and tools that are configured to receive will ignore the request payload. It is also necessary to send the completed notification from SOAtest after sending requests, even for server streaming method types that only take one request message. A tool configured to receive the completed notification will wait for that event or report an error if another response message is received. This allows SOAtest to consume a dynamic number of response messages from a gRPC stream by checking if the stream has completed inside of a looping test suite.
Change Log
1.5
- Support client certificates for two-way SSL
1.4
- Added support for large inbound messages
1.3
- Decode grpc-status-details-bin header to JSON when both Protobuf and gRPC extensions are loaded
...