Local security

Local security provides protection for WebSphere MQ Everyplace data or MQeFields objects, including message, MQeMsg, objects. The protected data is returned in a byte array. To apply local security to a data object you must:

  1. Create an attribute with an appropriate authenticator, cryptor, and compressor
  2. Set up an appropriate key (by providing a password or passphrase seed)
  3. Explicitly attach the key to the attribute, the attribute to the data (MQeFields) object, and invoke the dump() function on the data object

The authenticator determines how access to the data is controlled. The cryptor determines the cryptographic strength protecting the data confidentiality. The compressor determines the storage required by the message.

WebSphere MQ Everyplace provides the MQeLocalSecure class to assist with the use of local security. However, it is the responsibility of the local security user to setup an appropriate attribute and provide the password or passphrase key. MQeLocalSecure provides the function to protect the data and to save and restore it from backing storage. If an application chooses to attach an attribute to a message without using MQeLocalSecure, it also needs to save the data after using dump and must retrieve the data before using restore.



© IBM Corporation 2000, 2003. All Rights Reserved