Administer default roles
Service integration bus security uses role-based authorization. By adding a user or a group to the default roles for a secured bus, we can control which users and group members have access to the bus and its resources in the default roles when messaging security is enabled.
The default roles are sender, receiver, browser, and creator. These roles apply to bus destinations that do not have a destination role, or have been configured to inherit the default roles. By default, all destinations inherit the default roles. Access in the default roles exists in addition to any specific access roles that have been configured for a destination.
Subtopics
- List users and groups in default roles
Service integration bus security uses role-based authorization. By listing the users and groups in the default roles for a selected secured bus, we can find out which users and group members are authorized to perform messaging operations on a local bus destinations that is allowed to inherit default roles.- Add users and groups to default roles
Service integration bus security uses role-based authorization. By adding selected users and groups to the default roles for all the local bus destinations on a secured bus, we provide those users and group members with access to the local bus destinations allowed to inherit default roles.- Removing users and groups from default roles
Service integration bus security uses role-based authorization. By removing selected users and groups from the default roles for a selected secured bus, you prevent those users and group members from accessing the bus using the default roles.
Related:
Role-based authorization Destination security Access role assignments for bus security resources Default access roles [Settings]