10.3 Understanding OIF Basic and Advanced Deployments

10.3.1 Basic Deployment

The Basic deployment includes Oracle Identity Federation with minimum functionality enabled and the following configuration:

• No User Data Store

• No Federation Store

• JAAS Authentication Engine

• Test Service Provider (SP) Engine

• Memory Session Data Store

• Memory Message Data Store

• XML file system Configuration Store

10.3.2 Advanced Deployments

The Advanced deployments allows you to choose between different types of data stores and authentication engines. The following is a list and description of the types of data stores and authentication engines you can choose during an Advanced installation:

Authentication Engine

• JAAS: Delegates authentication to the application server.

• LDAP: Uses form login and LDAP bind with credentials supplied by user to authenticate against LDAP repository.

User Data Store

• None: No User Data Store. Typically used with Custom or JAAS Authentication Engines, environments without user attributes, or Windows CardSpace.

• LDAP: Typical configuration that stores user data in an LDAP repository.

• RDBMS: Uses database tables with user names (and optionally user attributes) in columns.

Federation Data Store

• None: No Federation Data Store. Typically used when there are no persistent account linking records. No Federation Data Store is also an alternative to using name identifiers, such as e-mail address, X.509 DN, Kerberos, or Windows Name Identifier.

• LDAP: Stores federation in an LDAP repository. Commonly deployed when the User Data Store is also LDAP.

• RDBMS: Stores federation in a relational database repository. Commonly deployed when the User Data Store is also RDBMS.

• XML: Stores federation data in an XML file system. Commonly used for testing purposes.

User Session Store and Message Store

• Memory: Stores transient runtime session state data and protocol messages in in-memory tables. Commonly used for single instance deployments. Memory provides better performance than the RDBMS User Session Store, but increases runtime memory requirements.

• RDBMS: Stores transient runtime session state data and protocol messages in a relational database. Recommended for High Availability cluster environments.

Note:

User Session Store and Message Store appear in the Installer as separate configuration items, however, most deployments use the same type of repository for both stores.

Configuration Data Store

• File System: Stores Oracle Identity Federation configuration data on the local file system. Commonly used in single-instance and testing environments.

• RDBMS: Stores Oracle Identity Federation configuration data in a relational database. Commonly used in High Availability environments or single-instances with failover redundancy.