Authentication Engines - JAAS

Configuring Oracle Identity Federation 5-103 View Custom Engines Use the View button to organize the table of custom engines. You can change the column order of the display and specify which fields to include or exclude. The Reorder Columns dialog allows you to select any field and use the arrows to reposition it in the table. Add an Engine Click Add to add a new custom engine. You are asked to provide a unique engine name; an Engine ID is automatically generated. Once the engine is added, you can add this information: ■ Enabled - Check the box to enable the engine, or uncheck to disable it. ■ Web Context - Specifies the Web application context in which your custom authentication engine is deployed. ■ Authentication Relative Path - Specifies the path to your custom authentication engine, relative to the Web context. ■ Logout Relative Path - Specifies the path to the logout service if any for your custom authentication engine, relative to the Web context. For example, auth_ enginesmyAuthLogout.jsp. 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, or 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. 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.16 Configuring SP Integration Modules

Use this page to configure the SP integration module for Oracle Identity Federation. This page consists of tabs devoted to individual SP integration module. Updates on any tab are saved as you move to other tabs. When you are done, click Apply to save the changes, or Revert to reset the data to its previous state. See Also: Section 10.3, Creating a Custom Authentication Engine 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.