Policy agent update 2.2–02 includes fixes and enhancements released in hot patches since the Policy Agent 2.2–01 update. Consider updating to a new 2.2-02 agent if you have not updated your agent with any of these recent hot patches, or if you need any of the fixes or enhancements in the update.
Version 2.2–02 web and J2EE policy agents supersede the respective version 2.2 and 2.2–01 agents.
Support for Policy Agent 2.1 is being dropped, as noted in Deprecation Notifications and Announcements.
The following Access Manager Policy Agent 2.2-02 web agents are available on the Sun Downloads page under Identity Management: http://www.sun.com/download/.
Policy Agent 2.2-02 for Apache Web Server 2.0.54
Policy Agent 2.2-02 for Apache 2.2.9
Policy Agent 2.2-02 for IBM Lotus Domino Server 6.5 / 7.0
Policy Agent 2.2-02 for Microsoft IIS 5.0
Policy Agent 2.2-02 for Microsoft IIS 6.0
Policy Agent 2.2-02 for Sun Java System Web Server 6.1
Policy Agent 2.2-02 for Sun Java System Web Server 7.0
Policy Agent 2.2-02 for Web Proxy Server 4.0
Large file support is added for the Apache 2.0 agent. Support for the large file option is specifically needed because the latest versions of the Solaris 10 OS, both SPARC and x86 platforms, include a pre-installed Apache server with large file support enabled.
With update 2.2-02, two shared objects are included with the Apache agent:
libamapc2.largefile.so - The Apache server was built with the large file option enabled.
libamapc2.so - The Apache server was built with the large file option not enabled.
Non-large file support is the default. For an Apache 2.0 server with the large file option enabled, you might need to backup libamacp2.so and then copy libamapc2.largefile.so to the location of libamapac2.so.
To check for the large file option, use apxs -q CFLAGS. If the large file option is enabled, the command shows -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64. The agent's large file supported library is built using these compiler flags.
Important: If third-party components such as php or mod_perl are deployed on an Apache server that is built with the large file option set, these components also need to be compiled with the large file options set. Generally, use the Apache server header files during the compilation of these third-party components. Header files that are generated by Apache after enabling the large file support need to be used in these compilations.
In addition to the platforms listed in Supported Servers for Web Agents in Policy Agent 2.2, the following new platforms are added for web agents in the 2.2–02 update.Table 4 New Platform Support for 2.2-02 Web Agents
2.2-02 Web Agent
New Supported Platform
All 2.2-02 web agents
Red Hat Enterprise Linux 5.0, 32–bit and 64–bit systems
Apache Web Server 2.0.54
Solaris 10 OS, SPARC platform, 64–bit systems
Solaris 10 OS, SPARC platform, 64–bit systems
Sun Java System Web Server 6.1
Solaris 9 and 10 OS, x86 platform, 32–bit systems
IBM Domino Server 6.5
IBM Domino Server 7.0
IBM Domino Server 8.0
IBM AIX 5.3
The following Access Manager Policy Agent 2.2-02 J2EE agents are available on the Sun Downloads page under Identity Management: http://www.sun.com/download/.
Apache Tomcat 6.0
Apache Tomcat 5.5 Servlet/JSP container
JBoss Application Server 4.0
IBM WebSphere Application Server 5.1.1
IBM WebSphere Application Server 6.0
BEA WebLogic Server 8.1 Service Pack 4
BEA WebLogic Server 9.0/9.1
BEA WebLogic Server 9.2
BEA WebLogic Server 10
IBM Domino Server 6.5/7.0
Oracle Application Server 10g
Sun Java System Application Server 8.1/8.2
Sun Java System Application Server 9.0/9.1
In addition to the platforms listed in Supported Servers for J2EE Agents in Policy Agent 2.2, the following new platforms are added for J2EE agents in the 2.2–02 update.
All version 2.2–02 J2EE agents on Red Hat Enterprise Linux AS 5.0, 32–bit and 64–bit, if the previous version of the agent was supported on Red Hat Enterprise Linux AS 3.0 and 4.0
Version 2.2-02 Apache Tomcat 6.0 agent on HP-UX 11i
If the filter mode (com.sun.identity.agents.config.filter.mode property) is set to J2EE_POLICY or ALL (which is the default value set during the agent installation), the version 2.2–02 Oracle Application Server 10g agent returns an error in the amFilter log when a protected resource is accessed.
Workaround. See the additional task in the Post-Installation Steps Specific to Agent for Oracle Application Server 10g in Sun Java System Access Manager Policy Agent 2.2 Guide for Oracle Application Server 10g.
For a J2EE agent, the Audit Log properties in AMAgent.properties are set as:
com.sun.identity.agents.config.audit.accesstype = LOG_DENY com.sun.identity.agents.config.log.disposition = ALL
If a user for whom the access is denied to a J2EE protected resource tries to access a the resource in a deployed application, access to the protected resource is denied, but there is no entry in the logs for the deny action on either the Access Manager or J2EE agent side.
Workaround. None. This is a limitation of the product. For a J2EE policy to be evaluated, the control is given to the web container on which the agent is deployed, to determine the access policies. The web container doesn't send the access decision back to the agent for a resource that is protected with J2EE security policies. The web container just denies the access, and the agent cannot effectively log when the access is denied.
Previously, a delay occurred for the Microsoft IIS 5.0 agent when a user accessed a protected resource. When the agents were deployed on multiple servers, serious performance degradation occurred.
Workaround. The Policy Agent 2.2–02 update includes the following new property:
If this property is set to 0 (the default value), you can prevent the delay for all agents.
For web agents, the sunwMethod parameter is removed from the URL in cross domain single sign-on (CDSSO) mode, because this parameter can cause problems with AJAX driven applications.
Web agents can use the following new property:
The default value is false, meaning that the sunwmethod parameter will not be used in CDSSO mode. For backward compatibility, if this property is set to true, CDSSO mode will function as it previously did.
The IBM Lotus Domino 7.0 agent previously displayed an internal server error (HTTP 500) if the Access Manager server was not responding.
Workaround. Set the following new property to the URL where you want the version 2.2–02 Lotus Domino 7.0 agent to redirect the client if the Access Manager server does not respond:
This new property also applies to the version 2.2–02 Apache 2.x agent.
When a web client accesses a resource and that request results in composite advice (sunamcompositeadvice) returned, the policy agent produces an auto-submitting HTML form, which can be difficult for a web client to interpret. Now, the following new property determines whether the composite advice is added in the query or through a POST request:
true: Composite advice will be added to the redirect URL.
false: Composite advice will be sent through a POST request.
The default is false.
The Apache 2.0 agent now recognizes these additional methods: VERSION_CONTROL, CHECKOUT, UNCHECKOUT, CHECKIN, UPDATE, LABEL, REPORT, MKWORKSPACE, MKACTIVITY, BASELINE_CONTROL, and MERGE. These methods are used for WebDAV versioning (RFC 3253) and specifically for a Subversion repository.
If the time on the web agent host machine differs from the Access Manager time, you might occasionally see an incorrect policy decision or an infinite re-direction. The following new property in AMAgent.properties adjusts the clock skew between the web agent and Access Manager machines:
This properties specifies the time in seconds used to adjust the time difference between the policy agent machine and the Access Manager machine, as follows:
Clock skew in seconds = AgentTime - AccessManagerTime
The default is zero (0).
You should also run a time syncing service to keep the time on the agent machine and the Access Manager machine as close as possible.