Sun OpenSSO Enterprise Policy Agent 3.0 Guide for Apache HTTP Server 2.0.x

Supported Platforms, Compatibility, and Coexistence for the Apache HTTP Server 2.0.x Agent

Supported Platforms for the Apache HTTP Server 2.0.x Agent

Table 1 Supported Platforms for the Apache HTTP Server 2.0.x Agent


Agent For	Support Platforms
Apache HTTP Server 2.0.x Oracle HTTP Server 10.1.x based on Apache HTTP Server 2.0.x IBM HTTP Server 6.0 and 6.1 based on Apache HTTP Server 2.0.x	Solaris OS on SPARC and x86 platforms, versions 9 and 10, 32–bit and 64–bit Red Hat Enterprise Linux Advanced Server 4.0 and 5.0, 32–bit and 64–bit Windows Server 2003 and 2008, 32–bit only Ubuntu 8.x Server Edition, 32-bit and 64-bit SuSE Linux 9.x, 32-bit and 64-bit Debian 4.x, 32-bit and 64-bit
Apache HTTP Server 2.0.x on IBM AIX® systems IBM HTTP Server 6.0 and 6.1 based on Apache HTTP Server 2.0.x	IBM AIX 5.x and 6.1, 32–bit only
Apache HTTP Server 2.0.x	HP-UX 11i v1 or later, 32–bit, with the integrated (built-in) Apache 2.0.x server only Note. The Apache HTTP Server 2.0.x agent is not supported on the Apache 2.0.x server manually installed on HP-UX.
Minor versions of the Apache HTTP Server 2.0.x web container, Oracle HTTP Server, and IBM HTTP Server are supported. Minor versions of the supported platforms, including updates, service packs, and patches, are also supported.

Compatibility With Access Manager 7.1 and Access Manager 7 2005Q4

Access Manager 7.1 and Access Manager 7 2005Q4 are compatible with version 3.0 policy agents. However, because Access Manager 7.1 and Access Manager 7 2005Q4 do not support centralized agent configuration, a version 3.0 agent deployed with Access Manager must store its configuration data locally in the OpenSSOAgentBootstrap.properties and OpenSSOAgentConfiguration.properties files. The OpenSSOAgentBootstrap.properties file contains the information required for the agent to start and initialize itself.

Coexistence With Version 2.2 Policy Agents

OpenSSO Enterprise supports both version 3.0 and version 2.2 agents in the same deployment. The version 2.2 agents, however, must continue to store their configuration data locally in the AMAgent.properties file. And because the version 2.2 agent configuration data is local to the agent, OpenSSO Enterprise centralized agent configuration is not supported for version 2.2 agents. To configure a version 2.2 agent, you must continue to edit the agent's AMAgent.properties file.

For documentation about version 2.2 agents, see http://docs.sun.com/coll/1322.1.

Unsupported OpenSSO Enterprise Features

The Apache HTTP Server 2.0.x agent does not support the following features:

Log File Rotation

The Apache HTTP Server 2.0.x agent does not support log file rotation, because the multi-process environment impairs the agent's capability to obtain the correct size of the log file. Without the correct log file size, the agent cannot rotate the file as intended.

Therefore, do not enable log rotation for the Apache HTTP Server 2.0.x agent, either in the OpenSSO Administration Console or by setting the com.sun.am.policy.agents.config.local.log.rotate property to true. Enabling log rotation can cause inconsistent and unpredictable results for the agent.

Notifications

The Apache HTTP Server 2.0.x agent does not support notifications, so maintaining the agent's SSO, policy, and configuration caches through a notification mechanism is not available.

Therefore, do not enable notifications for the Apache HTTP Server 2.0.x agent, either in the OpenSSO Administration Console or by setting the com.sun.identity.agents.config.notification.enable property to true. Enabling notifications can cause unpredictable behavior for the agent.

POST Data Preservation

The Apache HTTP Server 2.0.x agent does not support POST data preservation, where POST data is submitted to the server through HTML forms before users log in to OpenSSO Enterprise.