Role-based authorization

 

Use authorization information to determine whether a caller has the necessary privileges to request a service.

Web resource access from a Web client is handled by a Web collaborator. EJB resource access from a Java client is handled by an EJB Collaborator. The collaborators extract client credentials from the object request broker current object.

The resource and the received credentials are presented to WSAccessManager to check whether access is permitted to the client for accessing the requested resource.

The access manager module contains two main modules:

Module	Description
Resource permission	Helps determine the required roles for a given resource. It uses a resource to roles mapping table that is built by the security run time during application startup. To build the resource-to-role mapping table, the security run time reads the deployment descriptor of the enterprise beans or the Web module (ejb-jar.xml or web.xml)
Authorization table	Consults a role to user or group table to determine whether a client is granted one of the required roles. The role to user or group mapping table, also known as the authorization table, is created by the security run time during application startup. To build the authorization table, the security run time reads the application binding file (ibm-application-bnd.xmi file).

Use authorization information to determine whether a caller has the necessary privilege to request a service. You can store authorization information many ways. For example, with each resource, you can store an access-control list, which contains a list of users and user privileges. Another way to store the information is to associate a list of resources and the corresponding privileges with each user. This list is called a capability list.

WAS uses the J2EE authorization model. In this model, authorization information is organized as follows...

• During the assembly of an application, permission to invoke methods is granted to one or more roles. A role is a set of permissions; for example, in a banking application, roles can include Teller, Supervisor, Clerk, and other industry-related positions. The Teller role is associated with permissions to run methods related to managing the money in an account, such as the withdraw and deposit methods. The Teller role is not granted permission to close accounts; this permission is given to the Supervisor role. The application assembler defines a list of method permissions for each role; this list is stored in the deployment descriptor for the application.

There are two special subjects that are not defined by J2EE: AllAuthenticatedUsers, Everyone. A special subject is a product-defined entity independent of the user registry. It is used to generically represent a class of users or groups in the registry.

• AllAuthenticatedUsers is a special subject that permits all authenticated users to access protected methods. As long as the user can authenticate successfully, the user is permitted access to the protected resource.

• Everyone is a special subject that permits unrestricted access to a protected resource. Users do not have to authenticate to get access; this special subject provides access to protected methods as if the resources were unprotected.

During the deployment of an application, real users or groups of users are assigned to the roles. The application deployer does not need to understand the individual methods. By assigning roles to methods, the application assembler simplifies the job of the application deployer. Instead of working with a set of methods, the deployer works with the roles, which represent semantic groupings of the methods. When a user is assigned to a role, the user gets all the method permissions that are granted to that role. Users can be assigned to more than one role; the permissions granted to the user are the union of the permissions granted to each role. Additionally, if the authentication mechanism supports the grouping of users, these groups can be assigned to roles. Assigning a group to a role has the same effect as assigning each individual user to the role.

A best practice during deployment is to assign groups, rather than individual users to roles for the following reasons...

• Improves performance during the authorization check. Typically far fewer groups exist than users.

• Provides greater flexibility, by using group membership to control resource access.

• Supports the addition and deletion of users from groups outside of the product environment. This action is preferred to adding and removing them to WAS roles. Stop and restart the enterprise application for these changes to take effect. This action can be very disruptive in a production environment.

At run time, WAS authorizes incoming requests based on the user's identification information and the mapping of the user to roles. If the user belongs to any role that has permission to execute a method, the request is authorized. If the user does not belong to any role that has permission, the request is denied.

The J2EE approach represents a declarative approach to authorization, but it also recognizes that you cannot deal with all situations declaratively. For these situations, methods are provided for determining user and role information programmatically. For Enterprise JavaBeans, the following two methods are supported by WAS...

getCallerPrincipal:	Retrieves the user identification information.
isCallerInRole:	Checks the user identification information against a specific role.

For servlets, the following methods are supported by WebSphere Application Server:

• getRemoteUser
• isUserInRole
• getUserPrincipal

These methods correspond in purpose to the enterprise bean methods.

 

See Also

Admin roles
Naming roles

 

---