Use this guide along with theData Tab Configurationguide to configure a SecureAuth IdP realm that uses Oracle Database as an additional Profile Provider.
An on-premises Oracle Database with which SecureAuth IdP can integrate SecureAuth IdP supports versions 11.2 and 12.1, and supports with limitations versions 11.1 and 10.2
Create or enable an admin account that has read access (and optional write access) to the tables and stored procedures Write access is required to update user profile information, such as creating new users and changing passwords
1. In the Profile Provider Settings section, select True from the Same as Above dropdown to copy the data store integration from the Membership Connection Settings section for use in profile connection; or select False if that directory is only used for the membership connection.
2. Select Oracle from the Default Profile Provider dropdown if Oracle is to be used as the default profile provider
If another Oracle data store is configured in the Membership Connection Settings section, and True is selected from the Same as Above dropdown, then those settings appear in the Profile Connection Settings (below) and must be modified to reflect the settings of the new Oracle data store
Only one Oracle can be utilized for profile connection
If another directory is selected from the Default Profile Provider dropdown, then Oracle must be selected from Source dropdown in the Profile Fields section for the SecureAuth IdP Properties that are mapped to Oracle fields