Click Add, and select the authentication mechanism and the identity provider to

5-102 Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation Use the Enable Authentication Engine check-box to enable or disable this engine. Since JAAS is the default engine, this box is checked by default. To disable the JAAS authentication engine, another engine must be available to serve as the default engine. If necessary, first set up a different authentication engine, then return to this tab to disable the JAAS 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. Creating and Adding Users to the oifusers Group For a user to be authenticated by the JAAS authentication engine, a corresponding user entry must exist in the security realm of the WLS Domain where Oracle Identity Federation is deployed, and must be part of the oifusers group. Follow these steps to create the oifusers group and add new users. 1. Log in to Oracle WebLogic Servers Administration Server console.

2. On the left-hand pane, select Security Realms and navigate to myrealm, then

Users and Groups , then Groups.

3. Click New and enter name oifusers.

4. Navigate to Users and Groups, then Users.

5. Click New and select a name and password.

6. Click the user you just created and select the Groups tab.

7. Select group oifusers and move it to the Chosen column. Click Save.

To enter additional users, repeat steps 4-7. After the group and users have been created, you must restart the Administration server and managed server where Oracle Identity Federation is running in order for the changes to take effect.

5.15.10 Authentication Engines - Custom

On this tab, you can set up a custom authentication engine. Note: The JAAS authentication engine does not support logout. This means that after you configure a provider to use the engine, perform single sign-on between IdP and SP, and issue the Oracle Identity Federation logout URL http:host:portfeduserlogout, the user is not logged out and can repeat the SSO flow without having to log in again. See Also: Getting Started Managing Oracle Fusion Middleware 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