+

Search Tips   |   Advanced Search

Administer destination roles

Service integration bus security uses role-based authorization. When messaging security is enabled, users and groups must have authority to undertake messaging operations, at a bus destination. By administering destination roles, we can control which users and groups can undertake operations at a bus destination, and the types of operations that they can perform.

We use the administrative console to administer users and groups in access roles for a destination. The access roles available for a destination depend on the type of destination. The following table lists the roles that we can assign for each destination type:

Destination type Access roles
queue sender, receiver, browser, creator
port sender, receiver, browser, creator
webService sender, receiver, browser, creator
topicSpace sender, receiver
foreignDestination sender
alias sender, receiver, browser

In addition to controlling which users and groups have access to a specific local or foreign destination, we can also control the inheritance of access roles for a specific local destination. In this case, the default access roles that apply to all the destinations in the local bus namespace are added to any access roles that have been added for a specific destination.


Subtopics


Related:

  • Destination security
  • Topic security
  • Role-based authorization
  • Messaging security
  • Bus destinations
  • List bus destinations
  • Create a bus destination
  • Configure bus destination properties
  • Configure mediations
  • Configure a destination forward routing path
  • Configure a destination reverse routing path
  • Configure context properties for a bus destination
  • Deleting a bus destination
  • Resetting a destination
  • Administer foreign bus roles
  • Administer access to foreign destinations
  • Access role assignments for bus security resources
  • Destinations access roles [Collection]