IBM WebSphere V5.0 Security - CGISecurity

Security role mapping in the Administrative Console
Security role mapping can be performed from the WebSphere Administrative
console during application installation, or at any time once the application has
been installed.
Note: This section assumes that the user registry is set and configured for
LDAP. For more information on user registry settings, refer to Section 10.4,
“Configuring a user registry” on page 244.
When installing an application using the WebSphere Administrative Console, one
of the installation steps is to verify or define security role mapping. If security role
mapping has been previously defined in the application’s deployment descriptor,
the console will display that mapping and allow it to be modified.
Note: If no security roles are defined in the application deployment descriptor,
this step is omitted from the application installation steps.
After an application has been installed, the security role mapping console can be
accessed by following these steps:
1. Click Applications -> Enterprise Applications.
2. Click the name of the application you wish to modify.
3. Under Additional Properties, click Map security roles to users/groups.
The Security Role mapping console appears as shown in Figure 3-6 on page 33.
In this example, the manager role is mapped to managergrp, the clerk,
consultant, accountant roles are also mapped to the according groups; the
mdbuser role is mapped to a user, mdbuser; the allauthenticated role is mapped
to the All Authenticated special subject; and the everyone role is mapped to the
Everyone special subject.
Note: Assign the special subjects All Authenticated and Everyone as the last
setting before you click Next; you will then not lose these settings when you
look up users or groups.
32 IBM WebSphere V5.0 Security Handbook