
Protecting Web and Enterprise JavaBeans Modules
6
89
n
ov
do
cx (e
n)
16
Ap
ril 20
10
6
Protecting Web and Enterprise
JavaBeans Modules
The J2EE Agent mechanisms for protecting Web and EJB (Enterprise JavaBeans) modules have far
more granularity than what you can configure on the J2EE application server. With the agent, you
can be selective of what you are protecting. For a Web application, you can select to protect a
specific page or group of pages. For an Enterprise JavaBean, you can select to protect a bean, an
interface, a method, or a parameter. After selecting the granularity of the resource you want to
protect, you can then configure a policy that grants access to this resource. You can use roles as part
of this policy, but you can refine it by using other criteria such as LDAP attributes, credential profile
attributes, or the day of the week.
The J2EE Agent also allows you to decide how you want the authorization to be handled. You can
use the security settings configured on the application server, use the Authorization policies
configured on the J2EE Agent, or use both methods.
The following sections explain how to set up security for your J2EE resources:
Section 6.1, “Configuring Access Control,” on page 89
Section 6.2, “Protecting Web Resources,” on page 90
Section 6.3, “Protecting Enterprise JavaBeans Resources,” on page 92
6.1 Configuring Access Control
The access control configuration determines which Authorization policies are used to allow access
to resources. The application server must be configured to allow the J2EE Agent to enforce
authorization:
Section 4.2, “Configuring Applications on the JBoss Server,” on page 69
Section 4.3, “Configuring Applications on the WebSphere Server,” on page 71
Section 4.4, “Configuring Applications on the WebLogic Server,” on page 84
After you have configured the J2EE server for authorization, you need to configure the J2EE Agent
for access control:
1
In the Administration Console, click
Devices > J2EE Agents
>
Edit
.
2
In the
Access Control Configuration
section, select one or more of the following:
Enforce application server policy:
Allows access based on the policy of the application
server. These policies are defined on the application server in a
web.xml
file for a
.war
file and
in a
ejb-jar.xml
file for a
.jar
file.
IMPORTANT:
If you select this option and you are using a JBoss server, see
Section 4.2.2,
“Configuring Security Constraints,” on page 70
for additional information.
Содержание Access Manager 3.1 SP 2
Страница 4: ...4 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...
Страница 8: ...8 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...
Страница 44: ...44 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...
Страница 83: ...Preparing the Applications and the J2EE Servers 83 novdocx en 16 April 2010...
Страница 108: ...108 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...