To delete an HTTP header:

5-92 Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation ■ Logout Enabled - Check this box to indicate that Oracle Identity Federation will redirect the user to the Oracle SSO Logout URL when the Oracle Identity Federation logout flow is performed. The logout URL needs to be the Oracle SSO Logout URL: https:sso-host:sso-portssologout 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.

5.15.3 Authentication Engines - Oracle Access Manager

The tab contains these fields: ■ Default Authentication Engine - This is the engine used for authentications. The list-box contains all the currently enabled engines; selecting an engine from the list makes it the default engine. ■ Enable Authentication Engine - Check this box to enable the engine, and uncheck the box to disable the engine. If enabled, this engine appears on the list of available engines in the list-box associated with Default Authentication Engine. ■ User Unique ID Header - When Oracle Identity Federation uses Oracle Access Manager as an authentication engine, WebGate is integrated with Oracle HTTP ServerOracle Identity Federation and protects an Oracle Identity Federation URL. The policy domain for the Oracle Identity Federation URL is configured so that it will provide the user identifier as an HTTP header. Use this field to specify the name of the HTTP header containing the user identifier provided by WebGate. ■ Logout Enabled - Check this box to enable logouts with this engine. When enabling logouts, related fields include: – Clear Cookie - If checked, resetting the Oracle Access Manager cookie is sufficient for Oracle Identity Federation to log the user out of the Oracle Access Manager domain. – Cookie Domain - Cookie domain that Oracle Identity Federation will set when creating the Oracle Access Manager cookie. – Redirect to Logout URL - Check this box and fill in the URL if Oracle Identity Federation needs to redirect the user to a specific URL for Oracle Access Manager logout. – Logout URL - This is the URL to present at logout. Configuring Oracle Identity Federation 5-93 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.

5.15.4 Authentication Engines - LDAP Directory

The tab contains these fields: ■ Default Authentication Engine - This is the engine used for authentications. The list-box contains all the currently enabled engines; selecting an engine from the list makes it the default engine. ■ Enable Authentication Engine - Check this box to enable the engine, and uncheck the box to disable the engine. If enabled, this engine appears on the list of available engines in the list-box associated with Default Authentication Engine. ■ Connection URLs - space-delimited list of LDAP server URLs - hostname and port ■ Bind DN - This is the DN used by the Oracle Identity Federation server to connect to the LDAP server. For example: cn=fedid,dc=mycompany,dc=com ■ Password - Server password ■ Confirm Password - Server password ■ Maximum Connections - This is the maximum number of concurrent connections made by Oracle Identity Federation to the LDAP server. ■ User Credential ID Attribute - This is the attribute with which Oracle Identity Federation will authenticate the user. For example, if the attribute configured here is mail, and the value of this attribute for a user is alicemycorp.com, that user will need to authenticate with username alicemycorp.com. ■ User Unique ID Attribute - This is the attribute with which Oracle Identity Federation will identify the user. Note: The attribute value configured here must be unique across all users.