All Downloads are FREE. Search and download functionalities are using the official Maven repository.

en.help.task-protocolssledit.html Maven / Gradle / Ivy



To Edit SSL Settings for a Protocol

Before You Begin

This task is meaningful only if security has been enabled for the protocol.

  1. In the navigation tree, expand the Configuration node.

  2. Under the Configuration node, expand the Network Config node.

  3. Under the Network Config node, select the Protocols node.

    The Protocols page opens.

  4. On the Protocols page, click the name of the protocol that you are editing.

    The Edit Protocol page opens.

  5. On the Edit Protocol page, click the SSL tab.

    The SSL page opens.

  6. Select the TLS1.0 Enabled checkbox to enable Transport Layer Security 1.0(TLS1.0).

    This option is enabled by default.

  7. Select the TLS1.1 Enabled checkbox to enable Transport Layer Security 1.1(TLS1.1).

    This option is enabled by default.

  8. Select the TLS1.2 Enabled checkbox to enable Transport Layer Security 1.2(TLS1.2).

    This option is enabled by default.

  9. Select the TLS1.3 Enabled checkbox to enable Transport Layer Security 1.3(TLS1.3).

    This option is enabled by default.

  10. Select the Client Authentication Enabled checkbox to require clients to identify themselves to the server on every request.

    This option is disabled by default.

  11. In the Certificate Nickname field, type the nickname of the server certificate in the certificate database or the PKCS#11 token.

    In the certificate, the name format is tokenname:nickname. Including the tokenname: part of the name in this attribute is optional.

  12. In the Key Store field, type the name of the keystore file (for example, keystore.jks).

  13. In the Trust Algorithm field, type the name of the trust management algorithm (for example, PKIX) to use for certification path validation.

  14. In the Max Certificate Length field, type the maximum number of non-self-issued intermediate certificates that can exist in a certification path.

    This field is used only if the Trust Algorithm field is set to PKIX. A value of 0 implies that the path can only contain a single certificate. A value of -1 implies that the path length is unconstrained (there is no maximum). Setting a value less than -1 causes an exception to be thrown.

  15. In the Trust Store field, type the name of the truststore file (for example, cacerts.jks).

  16. In the Cipher Suites area, specify the cipher suites to be used.

    If you do not add any cipher suites, all cipher suites will be used.

  17. Click OK.

See Also
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices




© 2015 - 2024 Weber Informatics LLC | Privacy Policy