47 lines
3.1 KiB
HTML
47 lines
3.1 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head>
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
|
|
|
<title>Deploy secured applications</title>
|
|
</head>
|
|
|
|
<BODY>
|
|
<!-- Java sync-link -->
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
|
|
|
<h2><a name="secdep"></a>Deploy secured applications</h2>
|
|
|
|
<p>Deploying applications that have security constraints (secured applications) is not much different than deploying applications without any security constraints. The only difference is that you may need to assign users and groups to roles for a secured application, which requires that you have the correct active registry.</p>
|
|
|
|
<p>If you are installing a secured application, roles are defined in the application. You then assign users and groups to these defined roles.</p>
|
|
|
|
<p>These steps are common for both installing an application and modifying an existing application. If the application contains roles, the application installation wizard in the WebSphere administrative console prompts you to map security roles to users and groups. (You can also perform this step when you manage installed applications.)</p>
|
|
|
|
<p>To install (or deploy) your secured application, perform these steps in the WebSphere administrative console:</p>
|
|
|
|
<ol>
|
|
<li><p>Click <strong>Applications --> Install New Application</strong>.</p></li>
|
|
|
|
<li><p>Complete the non-security related steps prior to the step entitled <strong>Map security roles to users and groups</strong>.</p></li>
|
|
|
|
<li><p>Map security roles to users and groups. See <a href="secdpmap.htm">Assign users and groups to roles</a> for more information.</p></li>
|
|
|
|
<li><p>Complete the remaining steps to finish installing and deploying the application. If you are updating a previously installed application, stop the application and start it.</p></li>
|
|
</ol>
|
|
|
|
<p>After a secured application is deployed, make sure you can access the resources in the application with the correct credentials. For example, if your application has a protected Web module, make sure you only use the users listed in the roles for that Web resource to access.</p>
|
|
|
|
<p><strong>Updating and redeploying secured applications</strong></p>
|
|
|
|
<p>After an application is deployed, you can use the administrative console to modify the existing users and groups mapping to roles.</p>
|
|
|
|
<p>After you complete the changes, make sure to save the changes. Stop and start the application for the changes to become effective.</p>
|
|
|
|
<p>If you need to update any other security related information, use your development tool (such as WebSphere Studio) to modify roles, method permissions, auth-constraints, data-constraints, and other security-related information. After the changes are done, save the EAR file, uninstall the old application, deploy the modified application, and start the application to make the changes effective. If information about roles is modified make sure you update the user and group information using the administrative console.</p>
|
|
|
|
</body>
|
|
</html>
|
|
|