Authentication Engines - Custom

5-104 Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation ■ SP Integration module - Oracle Single Sign-On ■ SP Integration module - Oracle Access Manager ■ SP Integration module - Test SP Engine ■ SP Integration Module - Custom

5.16.1 SP Integration module - Oracle Single Sign-On

Use this tab to configure SP integration for Oracle Single Sign-On. The tab contains these fields: ■ Default SP Integration module - This is the module used for integration at the service provider. The list-box contains all the currently enabled engines; selecting an engine from the list makes it the default engine. ■ Enable SP module - Check this box to enable the module, and uncheck the box to disable the module. If enabled, this module appears on the list of available modules in the list-box associated with Default SP Integration module. ■ Authentication mechanism - authentication mechanism that will be used to locally authenticate users if Federated Identities are used during Federation SSO and if a Federation Record needs to be created during the SSO operation. ■ Username Attribute - Username Attribute that Oracle Identity Federation needs to provide to Oracle SSO. Default is uid. ■ Login URL - This is the Oracle Single Sign-On server URL to present at login. For example: http:sso_host:sso_portssoauth ■ Logout URL - This is the Oracle Single Sign-On server URL to present at logout. For example: http:sso_host:sso_portssologout ■ Logout Enabled – Enabledisable logout for the Oracle Single Sign-On application. The Regenerate button would create an encryption key that will be saved in a file and provided to the Oracle SSO Server. Updates you make on this tab are saved if you move to tabs for other authentication engines. When you are done, click Apply to save the changes, or Revert to reset the data to its previous state. Configuring Oracle Identity Federation 5-105

5.16.2 SP Integration module - Oracle Access Manager

Use this tab to configure SP integration for Oracle Access Manager. The tab contains these fields: ■ Default SP Integration module - This is the module used for integration at the service provider. The list-box contains all the currently enabled engines; selecting an engine from the list makes it the default engine. ■ Enable SP module - Check this box to enable the module, and uncheck the box to disable the module. If enabled, this module appears on the list of available modules in the list-box associated with Default SP Integration module. ■ Authentication mechanism - The authentication mechanism that will be used to locally authenticate users if federated identities are used during federation SSO and if a federation record needs to be created during the SSO operation. ■ Access Server SDK directory – Directory location of Access Server SDK. Absolute path or relative to DOMAIN_HOME. ■ Default Authentication Scheme – The authentication scheme in Oracle Access Manager that will be used as default scheme for the policy created by Oracle Identity Federation. ■ Cookie Domain - Cookie domain that Oracle Identity Federation sets when creating the Oracle Access Manager cookie. ■ Cookie duration - For a persistent cookie, the time in minutes during which the cookie will be valid; for a session cookie, enter 0. ■ Cookie Secured Flag Set - Check whether the cookie should be marked as secure: in this case, the browser will send the cookie over an HTTPS connection. ■ Logout Enabled – Enabledisable logout for the Oracle Access Manager application. See Also: Section 3.2.3.3, Integrate Oracle Access Manager as an SP Integration Module for details about configuring Oracle Access Manager as an SP integration engine.