SSL Settings

You can configure SSL at both the client and listener ends of the CENM stack. The presence of the SSL configuration entity enables the SSL communication between the two parties.

  • ssl: SSL settings.

    • keyStore: The services keyStore location.

      • location: Path to the location of the keyStore .jks - must be a fully resolvable path.

      • password: Password for the keyStore.

      • keyPassword: (Optional) Password for the key pair - can be omitted if it is the same as the keyStore password.

    • trustStore: (Optional) If a unique trust root is used (where all SSL keys are signed by a common root), then this keyStore must contain the certificate representing the public key of that root. The keyStore configured above contains a key pair signed by the root. Can be omitted if a single certificate and key pair is being used or the trust root certificate has been added to the keyStore.

      • location: Path to the location of the keyStore .jks - must be a fully resolvable path.

      • password: (Optional) Password for the trustStore. If not set, inherits the keyStore password.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.