Versions Compared

Old Version 1

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version Current

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2026.1

...

to insecure
Auth MechanismSpecify the authorization mechanism you want to use to connect to the gRPC server. Options are SSL and insecure. The default is insecure.
Certificate Chain File

Specify the path to a PEM-formatted certificate chain file. This field is ignored when the Auth Mechanism is set to to insecure.

Private Key File

Specify the path to the private key file is PKCS#8 format. This field is ignored when the Auth Mechanism is set

to insecure.

Client Private Key Password

If the private key is encrypted, specify its password. If the private key is not encrypted, leave this field blank.

Client Verification

Specify the level of authentication the server should expect from the client. Options are:

  • NONE: Clients will not present any identity.
  • OPTIONAL: Clients are requested to present their identity but clients without identities are permitted.
  • REQUIRED: Clients are requested to present their identity and are required to provide a valid identity.

The default is NONE.

Root Certificates File

Specify the path to a PEM-formatted root certificates file that should be used to verify the client's identity if it differs from the system's default.

Logging Settings

Scroll Table Layout
widths30%,70%

Log Level

Specify how much information you want logged to the console. The default is 2 (warn).

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

...