OAM 10g: Integrating Oracle Application Server Single Sign-On with Oracle Access Manager Step by Step (Doc ID 979827.1)

Last updated on MARCH 08, 2017

Applies to:

COREid Access - Version: 10.1.4.0.1 to 10.1.4.3.0 - Release: 10g to
Information in this document applies to any platform.

Goal

Provide a step by step process that was successfully used to enable single-sign on for the integration of Oracle Application Server Single Sign-On (OSSO) with Oracle Access Manager (OAM), that can be used as a guide line for the customer’s specific needs.

The following steps we derived from a specific environment. Some of the commands and or values used may need to be altered to fit your environments specific needs.

Environment Used
Steps Followed
1. Create a Java Class file
2. Edit the policy.properties file to use the new java class
3. Create an OAM Policy Domain that protects the Single-Sign On Login URL and sets an HTTP header variable.

How to do this is detailed in the following documents:
Oracle Application Server Single Sign-On Administrator’s Guide 10g (10.1.4.0.1), Chapter 14 Integrating with Third-Party Access Management Systems

Oracle® Access Manager Integration Guide 10g (10.1.4.2) Part Number E10356-01
Chapter 4 Integrating with Oracle Application Servers, 4.2.1.1 Creating the Java Class for Integration


Things to note...

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms