Configuration Guide › Relational Database Management › Important Notes When Configuring CA IdentityMinder for Relational Databases

Important Notes When Configuring CA IdentityMinder for Relational Databases

Before you configure CA IdentityMinder to manage a relational database, ensure that the database meets the following requirements:

• The database must be accessible through a JDBC driver or an Open Database Connectivity (ODBC) driver (when CA IdentityMinder integrates with SiteMinder). The driver must support outer joins. If more than two tables are used to represent a managed object, the driver must also support nested outer joins.

  Note: If the driver does not support outer joins, CA IdentityMinder uses inner joins when querying the database. This can cause unexpected query results.

• Uniquely identify each object that CA IdentityMinder manages, such as a user, group, or organization (when supported). For example, the unique identifier for users may be a login ID.

  Note: Make sure that the unique identifier is stored in a single column.

• CA IdentityMinder requires some multivalued attributes, which can be stored as a delimited list in a single cell or in multiple rows in a separate table. For example, the following tblGroupMembers table stores the members of a group:

The ID column contains the unique identifier for a group and the Members column contains the unique identifier for a member of the group. For example, dmason and rsavory are members of the Research group. When a new member is added to that group, another row is added to tblGroupMembers.

• When your environment includes organizations, do the following task:
  • Edit and run a SQL script, included with CA IdentityMinder, against the database to configure organization support.
  • CA IdentityMinder requires a top-level organization, named the root. All other organizations relate to the root organization.

    For more information about organization requirements, see Organizations Management.