en.help.task-protocolssledit.html Maven / Gradle / Ivy
Show all versions of console-web-plugin-help
To Edit SSL Settings for a Protocol
Before You Begin
This task is meaningful only if security has been enabled for the
protocol.
- In the navigation tree, expand the Configuration node.
- Under the Configuration node, expand the Network Config node.
- Under the Network Config node, select the Protocols node.
The Protocols page opens.
- On the Protocols page, click the name of the protocol that you are
editing.
The Edit Protocol page opens.
- On the Edit Protocol page, click the SSL tab.
The SSL page opens.
- Select the SSL3 Enabled checkbox to enable SSL3.
This option is enabled by default.
- Select the TLS Enabled checkbox to enable Transport Layer Security (TLS).
This option is enabled by default.
- Select the Client Authentication Enabled checkbox to require clients to identify themselves to
the server on every request.
This option is disabled by default.
- 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.
- In the Key Store field, type the name of the keystore file
(for example, keystore.jks).
- In the Trust Algorithm field, type the name of the trust management algorithm
(for example, PKIX) to use for certification path validation.
- 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.
- In the Trust Store field, type the name of the truststore file (for
example, cacerts.jks).
- 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.
- Click OK.
See Also
-
-
-
-
-
-
-
-
-
-
-
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices