User ID: The unique identifier with which the user will be identified in Oracle

5-98 Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation Example 2 Configuration The configuration corresponding to the table UserLoginInfo2 in Example 2 above is as follows. Suppose the JNDI name of the data source created for the database is MyCorpUserDS. ■ JNDI Name: MyCorpUserDS ■ Login Table: UserLoginInfo2 ■ Login ID Column: Username ■ User Unique ID Attribute: Username ■ Login Password Column: Password ■ Password Digest Algorithm: noneMD5SHA1

5.15.7 Authentication Engines - Infocard

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. ■ Map Assertion to User - If checked, the incoming assertion is mapped to a user record based on the configuration on the SAML 2.0 SAML 1.x Assertion tab of the Service Provider page. ■ Display one Entry per Infocard Provider - If checked, Oracle Identity Federation displays an infocard selection option for each Infocard provider configured in the Federations page. ■ Include Authentication Mechanism - If checked, Oracle Identity Federation adds the authentication mechanism as a required claim, enabling it to request a specific authentication method from the Infocard providers. ■ Authentication Mechanism Mapped to Personal Card Issuer - When the Infocard authentication engine is invoked for authentication with the authentication mechanism configured here, the personal issuer card is displayed on the login page. If invoked with an authentication mechanism different from the one configured here, all the Infocard providers are displayed. See Also: Section 6.12, Setting up Infocard . Configuring Oracle Identity Federation 5-99 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.8 Authentication Engines - Federated SSO Proxy

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. ■ Authentication Mechanism - This is the authentication mechanism that Oracle Identity Federation will use to authenticate the user locally when using the Federated SSO proxy. 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. Additional topics include: ■ About the Federated SSO Proxy Authentication Engine ■ Selecting the Identity Provider to Use ■ Configuring the Federated SSO Proxy Authentication Engine

5.15.8.1 About the Federated SSO Proxy Authentication Engine

When an identity provider uses the Federated SSO Proxy authentication engine to authenticate a user, it does this by taking the role of service provider, and initiating a Single Sign-On flow with a second identity provider that authenticates the user. The flow is as follows: WARNING: The authentication mechanism specified here must not map to the Federated SSO Proxy authentication engine. See Also: Section 5.15.8.1, About the Federated SSO Proxy Authentication Engine.