Assembling secured applications

 

+

Search Tips   |   Advanced Search

 

 

Overview

There are several assembly tools that are graphical user interfaces for assembling J2EE applications. Use these tools to assemble an application and secure EJB and Web modules in that application. An EJB module consists of one or more beans. We can enforce security at the EJB method level. A Web module consists of one or more Web resources (an HTML page, a JSP file or a servlet). We can also enforce security for each Web resource. Use an assembly tool to secure an EJB module (*.jar) or a Web module (*.war) or an application (enterprise archive (*.ear). We can create an application, an EJB module, or a Web Module and secure them using an assembly tool or development tools like the IBM Rational Application Developer.

 

Procedure

  1. Secure EJB applications using an assembly tool.

  2. Secure Web applications using an assembly tool.

  3. Add users and groups to roles while assembling secured application using an assembly tool.

  4. Map users to RunAs roles using an assembly tool.

  5. Adding the was.policy file to applications.

  6. Assemble the application components that you just secured using an assembly tool.

 

Result

After securing an application, the resulting .ear file contains security information in its deployment descriptor. The EJB module security information is stored in the ejb-jar.xml file and the Web module security information is stored in the web.xml file. The application.xml file of the application EAR file contains all the roles used in the application. The user and group to roles mapping is stored in the ibm-application-bnd.xmi file of the application EAR file.

The was.policy file of the application EAR contains the permissions granted for the application to access system resources.

The was.policy file of the application EAR contains the permissions granted for the application to access system resources protected by Java 2 security.

This task is required to secure EJB modules and Web modules in an application. This task is also required for applications to run properly when Java 2 security is enabled. If the was.policy file is not created and it does not contain required permissions, the application might not be able to access system resources.

 

What to do next

After securing an application, install an application using the administrative console.

 

See also


Enterprise bean component security
Securing enterprise bean applications
Web component security
Securing Web applications using an assembly tool
Role-based authorization
Adding users and groups to roles using an assembly tool
Mapping users to RunAs roles using an assembly tool

 

See Also


Java 2 security policy files

 

Related Tasks


Assembling applications
Adding the was.policy file to applications

 


 

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
Rational is a trademark of the IBM Corporation in the United States, other countries, or both.