Use these commands to specify which users can and cannot access destinations.
Users must be authorized to access all types of destination and to perform all types of operation (that is, send, receive, or browse) at a destination. These tasks allow you to control which users and groups belong to the roles for a specific local or foreign destination, and to allow or block the inheritance of permissions for a specific local destination.
The allowed roles for a destination depend on the type of the destination. The following table summarizes the role names that you can use when you are specifying the destinationType in a command.
Destination type | Allowed role names |
---|---|
queue | Sender, Receiver, Browser, Creator, IdentityAdopter |
port | Sender, Receiver, Browser, Creator, IdentityAdopter |
webService | Sender, Receiver, Browser, Creator, IdentityAdopter |
topicSpace | Sender, Receiver, IdentityAdopter |
foreignDestination | Sender, IdentityAdopter |
alias | Sender, Receiver, Browser, IdentityAdopter |
If the destination is a topic space, the permissions that you define are those on the topic space base.
A temporary destination has the same authorization permissions as the permanent prefix destination on which it is based. The name of the prefix destination appears as a prefix in the temporary destination's name. To access a temporary destination, users must be authorized to access the appropriate prefix destination.
For further information on administering destination permissions, refer to the following tasks: