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.
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
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.
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.
The fields in the Key section are available if you are configuring a protection token.
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.
Links marked (online) require access to the Internet.