EAServer provides component authorization through both roles and custom components:
Roles EAServer’s authorization model is based on roles. Define roles in EAServer Manager. Each role can include and exclude specific user names and digital certificates. If you use native operating system authentication, you can also include and exclude operating system group names; all users in the specified group are affected.
Roles are attached to EAServer packages, components, and methods. Attaching a role to a package controls access to all components in the package. To use a component, a user must be allowed component access by both the roles that are attached to the component and the roles that are attached to the package that contains the component.
See “Configuring EAServer roles” for more information on defining roles.
Custom components EAServer provides role and authorization service components with which you can create and install your own component to authorize clients to access resources on EAServer. See Chapter 10, “Creating and Using Custom Security Components.”
