Use this page to configure custom keystore files. Custom keystore files are alternatives to the key management support built into the WebSphere Application Server. The callback handler uses the custom version of the keystore configuration that includes keys.
You can configure custom keystore files for message parts when you are editing a default cell or server binding. You can also configure custom bindings for tokens and message parts that are required by the policy set.
Use this section to specify information about the custom keystores.
Specifies the full path to where the keystore file is located. Enter the path to the keystore file in this required field. You can use system variables for portions of the path. For example you might enter ${USER_INSTALL_ROOT}/etc/ws-security/myKeyStore.jks. This field is required for the custom keystore configuration.
Specifies the type of the keystore file to use.
Specifies the password to use.
Specifies the password to be use and confirms the one entered in the Password field.
Use this section to specify information about the key.
Specifies the name of the key to use. Enter the name of the key to be used in this required field.
Specifies the alias name of the key that you want to use. Enter the alias of the name of the key to use in this required field.
Specifies the password for the key that you want to use.
client | asymmetric signature outbound | AsymmetricBindingInitiatorSignatureToken0 |
client | asymmetric encryption inbound | AsymmetricBindingInitiatorEncryptionToken0 |
server | asymmetric signature outbound | AsymmetricBindingRecipientSignatureToken0 |
server | asymmetric encryption inbound | AsymmetricBindingRecipientEncryptionToken0 |
Specifies the confirmation of the password for the key that you want to use. Enter the password that you entered in the Password field to confirm.
Similar to the Password field, you cannot confirm the password for public keys for asymmetric signature inbound and encryption outbound.
Links marked (online) require access to the Internet.