WebSphere Message Brokers
File: ap01370_
Writer: Stephanie J Strugnell

Concept topic

This build: July 31, 2007 21:34:38

Authorization for configuration tasks

Authorization is the process of granting or denying access to a system resource. For WebSphere Message Broker, authorization is concerned with controlling who has permission to access WebSphere Message Broker resources, and ensuring that users who attempt to work with those resources have the necessary authorization to do so.

Examples of tasks that require authorization are:

Authorization for existing resources

If you want to use the security facilities of Version 6.0, when you require access to a resource that already exists, the user ID with which you work must be included in the Access Control List (ACL) for that resource.

For authorization to create resources, for example brokers, you must be a member of the Administrator local group.

The security architecture of WebSphere Message Broker is platform independent. If you are running in a heterogeneous environment, ensure that you limit all the principals you define for WebSphere Message Broker tasks to eight characters or fewer. If you have a Windows-only environment, you can create principals of up to twelve characters, but only use these longer names if you are sure that you will not later include a Linux, UNIX, or z/OS system in your WebSphere Message Broker network.

Related concepts
Authorization to access runtime resources
Related tasks
Setting up broker domain security
Enabling topic-based security
Canceling a deployment that is in progress
Related reference
Security requirements for administrative tasks
mqsicreatebroker command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:34:38

ap01370_ This topic's URL is: