Ensure all unprotected 2.x methods have the correct level of protection

Verify that the unprotected EJB v2.x methods have the correct level of protection before you map users to roles.

This administrative console page is displayed during the application deployment process. To access the administrative console page, click...

        Applications > New application > application_name. The page is displayed as Ensure all unprotected 2.x methods have the correct level of protection in the application deployment steps. On this administrative console page, we can specify whether users can access specific EJB modules.

To use this administrative console page, select the Uncheck, Exclude, or Role option, the check box next to the EJB module, and click Apply. If we select Role option, select the appropriate role for the EJB module before you click Apply.

Uncheck

Select this option if we do not want the application server to verify the access permissions for the EJB module. Everyone can access the EJB module.

Information	Value
Default:	Selected

Exclude

Select this option to protect this EJB module by making it inaccessible to users regardless of their access permissions.

Information	Value
Default:	Deselected

Role

The EJB level of protection based on the security role.

The roles listed in this menu are obtained from the application scope. If the selected role is not in the module, then it is added to the modules or JAR files.

Information	Value
Default:	Deselected

EJB module

Name of the module.

If a module name appears in this list, then the module contains unprotected EJB methods.

URI

The Uniform Resource Identifier (URI) used to locate the JAR file for the EJB module.

Protection type

Level of protection that is assigned to a particular module name.

After selecting the Uncheck, Exclude, or Role option and click Apply, the selected protection option is displayed in this column.

Assigning users and groups to roles

Assigning users to RunAs roles