Custom keystore settings
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.
We can configure custom keystore files for message parts when we are editing a default cell or server binding. We can also configure application specific bindings for tokens and message parts that are required by the policy set.
To view this administrative console page when we are editing a default cell binding:
- Click Services > Policy sets > Default policy set bindings.
- Click the WS-Security policy in the Policies table.
- Click the Authentication and protection link in the Main message security policy bindings section.
- Click a protection_token link in the Protection tokens table.
- Click the Callback handler link in the Additional bindings section.
- Select Custom from the list in the Keystore section.
- Click the Custom keystore configuration link.
To view this administrative console page when we are configuring application specific bindings for tokens and message parts that are required by the policy set:
- Click Applications > Application Types > WebSphere enterprise applications.
- Select an application containing web services. The application must contain a service provider or a service client.
- Click the Service provider policy sets and bindings link or the Service client policy sets and bindings in the Web Services Properties section.
- Select a binding. We must have previously attached a policy set and assigned an application specific binding.
- Click the WS-Security policy in the Policies table.
- Click the Authentication and protection link in the Main message security policy bindings section.
- Click a protection_token link in the Protection tokens table.
- Click the Callback handler link in the Additional bindings section.
- Select Custom from the list in the Keystore section.
- Click the Custom keystore configuration link.
This administrative console page applies only to JAX-WS applications.
Keystore
Use this section to specify information about the custom keystores.
Full path
Full path to where the keystore file is located. Enter the path to the keystore file in this required field. We can use system variables for portions of the path. For example we might enter ${USER_INSTALL_ROOT}/etc/ws-security/myKeyStore.jks. This field is required for the custom keystore configuration.
Type
Type of the keystore file to use.
Password
Password to use.
Confirm password
Password to be use and confirms the one entered in the Password field.
Key
Use this section to specify information about the key.
Name
Name of the key to use. Enter the name of the key to be used in this required field.
Alias
Alias name of the key to use. Enter the alias of the name of the key to use in this required field.
Password
Password for the key to use.
We cannot set a password for public keys for asymmetric signature inbound and encryption outbound. The Password and Confirm Password fields display only for the following:
Client or server Asymmetric value Key client asymmetric signature outbound AsymmetricBindingInitiatorSignatureToken0 client asymmetric encryption inbound AsymmetricBindingInitiatorEncryptionToken0 server asymmetric signature outbound AsymmetricBindingRecipientSignatureToken0 server asymmetric encryption inbound AsymmetricBindingRecipientEncryptionToken0
Confirm password
Confirmation of the password for the key to use. Enter the password entered in the Password field to confirm.
Similar to the Password field, we cannot confirm the password for public keys for asymmetric signature inbound and encryption outbound.
Define and manage policy set bindings Manage policy sets Protection token settings (generator or consumer) WS-Security authentication and protection Policy set bindings settings