Queue-based security

Queue-based security automatically protects WebSphere MQ Everyplace message data between the initiating queue manager and the queue, on the queue itself, and between the queue and the receiving queue manager. This form of protection requires the target queue to be defined with an attribute. This protection is independent of whether the queue is owned by a local or a remote queue manager.

A simple example of this is a target queue defined with an attribute that has an authenticator, an MQe3DESCryptor and an MQeRleCompressor. When such a target queue is accessed (either locally or remotely), using putMessage, getMessage or browseMessages, the queue attribute is automatically applied. In this example the application initiating the access has to satisfy the requirements of the authenticator before the operation is permitted. If the operation is permitted, the message data is automatically encoded and decoded using the attribute's MQe3DESCryptor and MQeRleCompressor. When the example target queue is remotely accessed, for example using putMessage, queue-based security automatically ensures that the message data is protected at the level defined by the queue attribute. This protection applies during transfer between the initiating queue manager and the queue, while the message is stored on the queue, and during transfer between the queue and the receiving queue manager.



© IBM Corporation 2000, 2003. All Rights Reserved