Save the changes. Update Oracle Identity Federation Configuration

3-4 Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation ■ Configure Oracle Single Sign-On ■ Testing Federated Single Sign-On Detailed instructions for these steps follow.

3.2.2.1 Create and Manage the Oracle HTTP Server Instance

To configure OHS, follow the instructions in Section 3.2.1, Deploying Oracle Identity Federation with Oracle HTTP Server .

3.2.2.2 Integrate Oracle Single Sign-On with OHS

This integration is necessary to deploy Oracle Identity Federation with Oracle Single Sign-On. Register Partner Application Start by registering the mod_osso module in 11g Release 1 11.1.1 OHS with the 10g Oracle Single Sign-On server as a partner application. For details on this procedure, refer to Configuring and Administering Partner Applications in the Oracle Application Server Single Sign-On Administrators Guide for 10g. You need to run ssoreg from the Oracle Single Sign-On server to generate an osso.conf file and manually copy it to the partner application AS_INST of the Oracle Identity Federation instance. Here is an example for registering a remote partner application on an Oracle Single Sign-On server: ORACLE_HOMEssobinssoreg.sh -site_name oif.server.com:7499 -config_mod_osso TRUE -mod_osso_url http:oif.server.com:7499 -remote_midtier -config_file oif.server.com.osso.conf Restart the OC4J_SECURITY instance of the Oracle Single Sign-On Server. After you run this command, a file named oif.server.com.osso.conf is created in the directory where the commmand was invoked. Copy that file to AS_ INSTconfigOHSOHS_NAME. Set Up mod_osso The next step is to set up mod_osso. Copy AS_INSTconfigOHSOHS_NAMEdisabledmod_osso.conf to AS_ INSTconfigOHSOHS_NAMEmoduleconf. All files in the moduleconf directory are read when OHS is started. Note: Oracle Identity Federation does not support the ability to force re-challenging the user for credentials when integrated with Oracle Single Sign-On, so that Oracle Identity Federation cannot support use cases where reauthentication must be forced. For example, if an SP sends an AuthnRequest with ForceAuthn=true to an Oracle Identity Federation IdP, and Oracle Identity Federation is integrated with Oracle Single Sign-On, the ForceAuthn flag is ignored.