Using a Version 2.2 Policy Agent After Upgrading to OpenSSO Enterprise

In this scenario, you have upgraded an Access Manager 7.x deployment to OpenSSO Enterprise 8.0 but you want to use an existing version 2.2 policy agent. Considerations are:

• Coexistence. Version 2.2 and version 3.0 policy agents can coexist in the same OpenSSO Enterprise deployment.

• Location of Agent Configuration Repository. A version 2.2 agent must continue to store its configuration data locally in its AMAgent.properties file on the agent's host server. Therefore, because the version 2.2 agent configuration data is local to the agent, the OpenSSO Enterprise centralized agent configuration feature is not supported for a version 2.2 agent. To configure a version 2.2 agent, you must continue to edit the agent's AMAgent.properties file.

• Deployment URI. If you are configuring a version 2.2 policy agent with OpenSSO Enterprise, the default Primary Server Deployment URI (and Failover Server Deployment URI, if required by the agent) is /opensso rather than /amserver.

• Agent Profile. You can create a version 2.2 Java EE (formerly J2EE) or web agent profile in the OpenSSO Enterprise Administration Console under Access Control, realm-name, Agents, and 2.2 Agents. However, you must configure the agent by editing its AMAgent.properties file.

• Realm Mode. If the Access Manager deployment was configured for Realm Mode, the realm name notation is changed in the URL after the upgrade to OpenSSO Enterprise. For example, if the Access Manager realm name was users, the name will be /users in OpenSSO Enterprise. You will need to reconfigure a version 2.2 policy agent to use the new realm name; otherwise. the “No such Organization found” message will be returned.

For more information about version 2.2 policy agents, see:

• Sun Downloads site under View by Category, Identity Management, and then Policy Agents: http://www.sun.com/download/index.jsp

• Documentation: http://docs.sun.com/coll/1322.1