IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Policy Sets and Policy Set Bindings editor: Key Information panel

Use this panel, which is in the Policy Set Bindings section of the editor, to further configure any message level protection tokens that are defined in the associated policy set.

The table is prefilled based on the selections made in the message part policy panel. Different combinations of message level protection tokens and message part protection tokens require one or more of the following types of additional information:

Key information in the form of a key name and key alias, for lookup in the broker keystore.
Verification information, which can be either trustany or truststore.

Where a message level protection token is displayed, enter the required level of information so that the policy set binding can be generated correctly in accordance with the associated policy set.

Configure the broker to refer to a keystore and truststore. You might also need to configure passwords for these stores, and specific key passwords. See Viewing and setting keystore and truststore runtime properties at broker level for further information.

Fields

Field name	Description and valid options
Token	Displays the names of any message level protection tokens that require further configuration. The token name is displayed after either request: or response:, depending on the configuration of the token in the associated policy set.
Key Name	The distinguished name (DN) that uniquely identifies the key in the keystore that is defined in the broker using the mqsichangeproperties command. For example `“CN=CommonName, O=Organisation, C=Country"`. When you require message level protection on the inbound signature token and the key is not known in advance, enter Any or leave blank.
Key Alias	The key alias of the key in the keystore defined by the broker. When you require message level protection on the inbound signature token and the key is not known in advance, enter Any or leave blank. You define the broker keystores using the mqsisetdbparms and mqsichangeproperties commands.
Trust	Either: TrustAny With no security profile set, all certificates are trusted. With a security profile set, the certificate is passed to the security provider defined by the security profile for it to establish trust. See Setting up message flow security. TrustStore Check against the public key certificates in the truststore defined by the broker.

ab60200_.htm |

Last updated Friday, 21 July 2017