IBM WebSphere V5.0 Security - CGISecurity

►
Session, entity, and message-driven bean methods can be delegated to
execute under the identity of either the caller (default), the EJB server, or a
specific security role. This is referred to as the Delegation Policy or Run-As
Mode Mapping.
In the next sections, each of these methods of applying security to EJBs will be
discussed in detail.
5.2 Defining J2EE roles for EJB modules
The method for defining security roles for EJBs and Web Components in the
Application Assembly Tool is the same. For example, to add a role named
manager to the EJB component, do the following:
1. Open the .ear file of the application, in our example: itsobank.ear.
2. Open the EJB Modules folder for your application, open the desired module
under it, itsobankEJB in our case, then finally select Security Roles.
3. If no security roles have previously been defined for EJBs, the box on the
right will be empty. Right-click the space under Name, and you will see the
pop-up menu. Select New to create a new security role.
4. In the New Security Role dialog, shown in Figure 5-1, enter the name of the
role, Manager, and (optionally) a description of the role.
Figure 5-1 Application Assembly Tool - New Security Role dialog box
5. Click Apply if you wish to add more security roles to the EJB component, or
click OK to close the New Security Role dialog box.
Chapter 5. Securing EJBs 75