Use this page to configure callback handler settings which determine how security tokens are acquired from messages headers.
You can configure callback handler settings 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.
When used in associated with a signature consumer, the alias supplied for the consumer is used strictly to retrieve the public key that is used to resolve an X.509 certificate that is not passed in the SOAP security header as a BinarySecurityToken. A password is not required.
The alias that is entered on a callback handler associated with an signature consumer must be accessible without a password. This means that the alias must not have private key information associated with it in the keystore.
See the topic Key
information settings for more information about the key identifier,
X.509 issuer/serial, and thumbprint.
The Callback Handler displays fields differently for different tokens being configured. Depending on whether you are configuring generator or consumer tokens for protection or you are configuring inbound or outbound tokens for authentication, the sections and fields on this panel display some or all of the fields explained in this topic, as noted in the description of each field.
The fields in the Class name section are available for all types of token configuration.
Select the class name to use for the callback handler. Select the Use built-in default option for normal operation. Use the Use custom option only if your are using a custom token type
Specifies that the default value is used for the class name. Use the default value (shown in the field) for the class name when you select this radio button. This name is based on the token type and whether the callback handler is for a token generator or a token consumer. This option is mutually exclusive to the Use custom option.
Specifies that a custom value is used for the class name. Select this radio button and enter the name in the field to use a custom class name.
No default value is available for this entry field. Use the information in the following table to determine this value:
Token Type | Consumer or Generator | Callback Handler Class Name |
---|---|---|
UsernameToken | consumer | com.ibm.websphere.wssecurity.callbackhandler.UNTConsumeCallbackHandler |
UsernameToken | generator | com.ibm.websphere.wssecurity.callbackhandler.UNTGenerateCallbackHandler |
X509Token | consumer | com.ibm.websphere.wssecurity.callbackhandler.X509ConsumeCallbackHandler |
X509Token | generator | com.ibm.websphere.wssecurity.callbackhandler.X509GenerateCallbackHandler |
LTPAToken/LTPAPropagationToken | consumer | com.ibm.websphere.wssecurity.callbackhandler.LTPAConsumeCallbackHandler |
LTPAToken/LTPAPropagationToken | generator | com.ibm.websphere.wssecurity.callbackhandler.LTPAGenerateCallbackHandler |
SecureConversationToken | consumer | com.ibm.ws.wssecurity.impl.auth.callback.SCTConsumeCallbackHandler |
SecureConversationToken | generator | com.ibm.ws.wssecurity.impl.auth.callback.WSTrustCallbackHandler |
This button is mutually exclusive to the Use built-in default option.
The fields in the Certificates section are available if you are configuring a protection token. For a consumer token, you can use the Trust any certificate or the Certificate store options to configure the certificate. For a generator token, you can click a certificate from the listing or click the New button to add one.
Specifies, if the protection token has a certificate configured, a to trust any certificate and not define the certificate store. Select this option to trust each certificate. This option is mutually exclusive to the Certificate store option and is only applicable to the token consumer.
Specifies, if the protection token has a certificate configured, the certificate store to be trusted. Select this option to trust each certificate store specified in the entry field. This option is mutually exclusive to the Trust any certificate option. When you select this option, the New button is enabled so that you can configure a new certificate store. You can also add a second certificate store to the Trusted anchor store entry field when you click Certificate store. The Trusted anchor store field is only applicable to the token consumer.
The fields in the Basic authentication section are available if you are configuring an authentication token that is not an LTPA Propagation token.
Specifies the password to be authenticated. Enter a password to authenticate in this entry field.
The fields in the Keystore section are available if you are configuring a protection token.
In the Keystore name list, you can click Custom to define a custom keystore, click one of the externally defined keystore names, or click None if no keystore is required.
Specifies the name of the centrally managed keystore file that you want to use.
Specifies a link to create a custom keystore. Click this link to open a panel where you can configure a custom keystore.
The fields in the Key section are available if you are configuring a protection token.
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.
You cannot set a password for public keys for asymmetric encryption generator or asymmetric signature consumer.
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.
Do not provide a key confirm password for public keys for asymmetric outbound encryption or inbound signature.
The fields in the Custom properties section are available for all types of token configuration.
You can add custom properties needed by the callback handler here using name-value pairs.
To implement signer certificate encryption when using the JAX-WS programming model, add the custom property com.ibm.wsspi.wssecurity.token.cert.useRequestorCert with the value true on the callback handler of the encryption token generator. This implementation uses the certificate of the signer of the SOAP request to encrypt the SOAP response. This custom property is used by the response generator.
Specifies the name of the custom property to use.
Custom properties are not initially displayed in this column. Click one of the following actions for custom properties:
Button | Resulting Action |
---|---|
New | Creates a new custom property entry. To add a custom property, enter the name and value. |
Delete | Removes the selected custom property. |
Specifies the value of the custom property to use. With the Value entry field, you can enter or delete the value for a custom property.