Click New Profile in the toolbar of the Profiles accordion.

23-12 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator Copy this file into the ODI_HOMEclientodibin directory. The Studio reads the identity store configuration and authenticates against the configured identity store. If you want to locate this file in a different location, edit the ODI_ HOMEclientodibinodi.conf file and edit the option that sets the location of the configuration file. This option is set in the following line: AddVMOption -Doracle.security.jps.config=.jps-config.xml Standalone Agent The configuration to connect and use the identity store is contained in an OPSS Configuration File called jps-config.xml file. Refer to the Oracle Fusion Middleware Application Security Guide for more information. Copy this file in the ODI_HOMEagentbin directory. The agent and the command line scripts will authenticate against the configured identity store. Java EE Components Oracle Data Integrator components deployed in a container Java EE Agent, Oracle Data Integrator Console do not require a specific configuration. They use the configuration of their container. See Configuring OAM Identity Assertion for SSO with Oracle Access Manager 10g in the Oracle Fusion Middleware Application Security Guide for more information on OPSS configuration in a Java EE context.

23.3.2.2 Setting the Authentication Mode

There are two ways to set or modify the password storage: ■ Creating the Master Repository allows you to define the authentication mode. ■ Switching the Authentication Mode modifies the authentication mode for an existing master repository.

23.3.2.3 Switching the Authentication Mode

Switching the authentication mode of the Oracle Data Integrator repository changes the way users authenticate. This operation must be performed by a Supervisor user. Use the Switch Authentication Mode wizard to change the user authentication mode. Before launching the Switch Authentication Mode wizard perform the following tasks: WARNING: When switching from an External to Internal authentication, user passwords are not copied from the identity store to the repository. The passwords are nullified. All the user accounts are marked as expired and must be reactivated by a SUPERVISOR that is created during the switch. When switching from Internal to External authentication, the users that exist in the repository and match a user in the identity store are automatically mapped. Users that do not match a user in the identity store are disabled. A Supervisor must edit the users so that their name has a match in the identity store. The context passwords are lost. Passwords for data servers, jdbc password of the work repository, and ESS related passwords are moved from a credential store to an other.