Integrating Oracle Access Manager with Oracle Single Sign On and Oracle Portal

describes and shows you how to integrate Oracle Access Manager with Oracle Single Sign On to enable user authentication to Oracle Portal
Overview

Oracle Access Manager (OAM) provides identity administration (using User, Group and Organization management, Self-service, Workflow capabilities, and delegated administration), Authentication and Authorization services, and Compliance reporting. By default, Oracle Single Sign On (OSSO) is the authentication provider for applications such as Oracle Portal. In this OBE, you will see how to integrate Oracle Access Manager with Oracle Single Sign On such that Oracle Portal can leverage Oracle Access Manager for Authentication Services.

Scenario

In this section, we integrate Oracle Access Manager with Oracle Application Server. More specifically, you integrate OAM with the Oracle Single Sign On server such that OSSO will delegate user authentication to OAM. All applications, such as Oracle Portal, will continue to seamlessly work with OSSO as if user authentication was being handled by OSSO, but instead, it is transparently being performed by OAM. This shows how OAM can co-exist with OSSO and all applications, such as Oracle Portal, which rely on OSSO for authentication services. User Authorization is still handled by the application itself, that is, Oracle Portal.

The following image highlights the setup/architecture for the complete OAM-OSSO-Portal integration scenario.

Performing the Preinstallation Requirements
Before you start the installation task, make sure that your system environment meets the following requirements:
Software Requirements
The system should include the following product:

Oracle Internet Directory 10g (10.1.4.0.1) (preinstalled): The user and partner data for the directory is stored under cn=Users,dc=mydopartners,dc=com and ou=vendors,dc=mydopartners,dc=com, respectively. For setting up the OID instance, note the following points:

You can refer to the Oracle Internet Directory 10g (10.1.4.0.1) installation guide from here.

You can use the staticports.ini file from below details ----

# J2EE and HTTP Server
Oracle HTTP Server port = 7777
Oracle HTTP Server Listen port = 7777
Oracle HTTP Server SSL port = 4443
Oracle HTTP Server Listen (SSL) port = 4443
Oracle HTTP Server Diagnostic port = 7200
Java Object Cache port = 7000
DCM Discovery port = 7100
Oracle Notification Server Request port = 6003
Oracle Notification Server Local port = 6101
Oracle Notification Server Remote port = 6200
Application Server Control port = 18100
Application Server Control RMI port = 18140
Oracle Management Agent port = 18120
Log Loader port = 44000
ASG port = 7890
# Infrastructure
Oracle Internet Directory port = 13060
Oracle Internet Directory (SSL) port = 13130
#Oracle Certificate Authority SSL Server Authentication port = port_num
#Oracle Certificate Authority SSL Mutual Authentication port = port_num
Enterprise Manager Console HTTP Port (orcl) = 5500
Enterprise Manager Agent Port (orcl) = 1830
# OracleAS Metadata Repository: Installation Port = 1521

These Changes will have to effect on SSO

SSO

SSO_HEADER_NAME