Create all the RunAs roles in your application. The user in the RunAs role can only be entered if that user or a group to which that user belongs is already part of the regular role.
Verify that the user registry requirements are met. These requirements are the same as those discussed in Assigning users and groups to roles. For example, if the role1 role is a role that is also used as a RunAs role, then the user1 user can be added to the RunAs role.
The administrative console checks this logic when Apply or OK is clicked. If the check fails, the change is not made and an error message is displayed at the top of the panel.
If the Everyone or All Authenticated special subjects are assigned to a role, a check does not occur for that role.
The checking is done every time you click Apply in this panel or when you click OK in the Map security roles to users/groups panel. The check verifies that all the users in all the RunAs roles do exist directly or indirectly through a group in those roles in the Map security roles to users/groups panel. If a role is assigned both a user and a group to which that user belongs, You can delete either the user or the group from the Map security roles to users/groups panel.
If the RunAs role user belongs to a group and if that group is assigned to that role, make sure that the assignment of this group to the role is done through the administrative console and not through an assembly tool or other method. When using the administrative console, the full name of the group is used (for example, hostname\groupName in Windows systems and distinguished names (DN) in Lightweight Directory Access Protocol
(LDAP)). During the check, all the groups to which the RunAs role user belongs are obtained from the user registry. Because the list of groups that are obtained from the user registry are the full names of the groups, the check works correctly.
If the short name of a group is entered using an assembly tool, for example group1 instead of CN=group1, o=myCompany.com, this check fails.
These steps are common to both installing an application and modifying an existing application. If the application contains RunAs roles,
you see the Map RunAs roles to users link during application installation and also during managing applications as a link in the Additional properties section.
Under Additional properties, click Map RunAs roles to users .
A list of all the RunAs roles that belong to this application display.
If the roles already have users assigned, they display here.
To assign a user, select the role. You can select multiple roles at the same time if the same user is assigned to all the roles.
Enter the user's name and password in the designated fields. The user name entered can be either the short name, which is preferred, or the full name, as seen when getting users and groups from the user registry.
Click Apply . The user is authenticated using the active user registry. If authentication is successful, a check is made to verify that this user or group is mapped to the role in the Map security
roles to users and groups panel. If authentication fails, verify that the user and password are correct and that the active registry configuration is correct.
To remove a user from a RunAs role, select the roles and click Remove .
ResultThe RunAs role user is added to the binding file in the application.
This file is used for delegation purposes when accessing J2EE resources. This step is required to assign users to RunAs roles so that during delegation the appropriate user is used to invoke the EJB methods.
What to do next
If you are installing the application, complete installation. After the application is installed and running, you can access your resources according to the RunAS role mapping. Save the configuration.
If you manage applications and modify the RunAs roles to users mapping, make sure you save, stop,
and restart the application so that the changes become effective. Try accessing your J2EE resources to verify that the new changes are in effect.