Deploying applications that have security constraints (secured applications) is not much different than deploying applications that do not contain any security constraints. The only difference is that you might need to assign users and groups to roles for a secured application. The secured application requires that you have the correct active user registry.
During the installation of a new application, the role definition is completed as part of the step that maps security roles to users and groups. If this assignment has already been completed by using an assembly tool, you can still confirm the mapping by going through this installation step. You can add new users and groups and modify existing information during this step.
If the application supports delegation, a RunAs role will already be defined in the application. If the delegation policy is set to Specified Identity during assembly, the intermediary invokes a method by using an identity setup during deployment. Use the RunAs role to specify the identity under which the downstream invocations are made. For example, if the RunAs role is assigned user bob and the client alice is invoking a servlet, with delegation set that calls the enterprise beans, the method on the enterprise beans is invoked with bob as the identity.
As part of the new application installation and deployment process, one of the steps is to map or modify users to the RunAs roles. Use this step to assign new users or modify existing users to RunAs roles when the delegation policy is set to Specified Identity.
To install and deploy the application, complete the following steps.