Mapping Roles for a Package

Configure package role mapping to authorize client requests to access MBOs and operations. Domain administrators can use a role mappings table to manage logical roles at the package level.

Note: If a developer has defined a logical role, mapping is not required; the logical role is matched to the physical role of the same name and is therefore automatically mapped.

See Roles and Mappings in Security for additional information.

  1. Open Sybase Control Center.
  2. Select and deploy an available package.
  3. Follow the wizard prompts until you reach the Configure Role Mapping page for the target package. Alternately, if you are editing package role mapping after deployment, select the Role Mapping tab from the Packages > < PackageName> node in the left navigation pane.
  4. Set an appropriate mapping state for each logical role. The state you choose allows you to disable logical roles (NONE), allow logical roles to be dynamically mapped (AUTO), or manually define which physical roles must be mapped to one or more logical roles (Map Roles). The states of AUTO or NONE require the least administration.
Related concepts
Subscriptions
Related tasks
Mapping Roles for a Domain
Deploying an MBO Package to a Domain
Selecting a Security Configuration for a Package
Managing Package Users