122
Novell Access Manager 3.1 SP2 J2EE Agent Guide
n
ov
do
cx (e
n)
16
Ap
ril 20
10
9.7 Unable to Federate WebSphere Custom
Profile If Agent Already Installed
When a WebSphere server instance that is created one machine is federated into the deployment
manager of another machine that already has server instances with J2EE Agent installed, the newly
federated server instance not start. This is because, the security configuration changes that are
performed apply to all the instances of the deployment manager and all the application server
instances that are part of it.
To work around this problem, copy the following files from the
$WAS_HOME$/lib
folder of the
machine that has agents installed, to the
$WAS_HOME$/lib
folder of the new machine, then restart
the server:
NidsCommonAgent-unsign.jar
NidsWebSphere-unsign.jar
nxpe.jar
jcc-unsign.jar
nxpe-toolkit-unsign.jar
9.8 Authorization Fails in the WebSphere
Application
Entries in the
NidsJaccRoles.xml
file indicate whether the
RunAs
roles and user/grouptorole
mappings are automatically propagated to the JAAC module. If you use SLES as your WebSphere
host, the file is located in a path similar to the following example:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/novell/cells/sles10Node01Cell/
nodes/sles10Nodeo1/servers/server1/NidsJaccRoles.xml
The entries look similar to the following:
<J2EERole roleId="Manager">
<User Name="
If you have configured WebSphere to map roles, the authorization of the user might occasionally
fail. This could be because, when
Run As
roles and user/grouptorole mappings are configured after
the J2EE Agent is installed, they fail to be propagated to the JAAC module even after a restart.
To workaround this issue:
1
Browse to the folder where the Novell J2EE Agent is installed.
2
Open
uDontKnowJacc.jy
, which is located in the
/novell/nids_agents/bin
folder.
3
Delete the first line.
4
Modify
member1
to
<application server name>
.
Replace
<application server name>
with the name of the application server instance where
NIDPJ2EEApp is installed.
5
6
Execute the following command at the shell prompt:
Содержание 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...