Integrate with Database User Management (DB2)

The Database User Management (DB2) connector integrates Oracle Access Governance with IBM DB2 database user management tables. You can establish a connection between IBM DB2 and Oracle Access Governance by entering connection details and configuring the connector. To achieve this, use the Orchestrated Systems functionality available in the Oracle Access Governance Console.

Prerequisites

Before you install and configure a Database User Management (DB2) orchestrated system, you should consider the following pre-requisites and tasks.

Certified Components

The DB2 system can be any of the following:

  • IBM DB2 UDB 9.x.

Supported Operations

The Database User Management (DB2) orchestrated system supports the following operations:
  • Create user
  • Add schema
  • Revoke schema
  • Add tablespace
  • Revoke tablespace

Create a DB2 System User Account for Database User Management (DB2) Orchestrated System Operations

Oracle Access Governance requires a user account to access the DB2 system during service operations. Depending on the system you are using, you can create the user in your system and assign specific permissions and roles to the user.

For DB2 database:

  1. Create a DB2 user agserviceuser at the OS level.
  2. Assign the following permissions and roles to the service user created:
    GRANT SELECT on TABLE syscat.schemata TO agserviceuser;

GRANT SELECT on TABLE syscat.tablespaces TO agserviceuser;

GRANT CREATEIN,DROPIN,ALTERIN ON SCHEMA 'SCHEMA_NAME' TO agserviceuser;

GRANT CONNECT,BINDADD,DBADM,CREATETAB,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT ON DATABASE TO agserviceuser;

Configure

You can establish a connection between IBM DB2 and Oracle Access Governance by entering connection details and configuring your database environment. To achieve this, use the Orchestrated Systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:
  1. From the Oracle Access Governance navigation menu icon Navigation menu, select Service Administration → Orchestrated Systems.
  2. Click the Add an orchestrated system button to start the workflow.

Select system

On the Select system step of the workflow, you can specify which type of database you would like to onboard.

  1. Select Database User Management (DB2).

Enter details

On the Enter Details step of the workflow, enter the details for the orchestrated system:
  1. Enter a name for the system you want to connect to in the What do you want to call this system? field.
  2. Enter a description for the system in the How do you want to describe this system? field.
  3. Determine if this orchestrated system is an authoritative source, and if Oracle Access Governance can manage permissions by setting the following checkboxes.
    • This is the authoritative source for my identities
    • I want to manage permissions for this system
    The default value in each case is Selected.
  4. Click Next.

Add owners

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources.

Note:

When setting up the first Orchestrated System for your service instance, you can assign owners only after you enable the identities from the Manage Identities section.
To add owners:
  1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
  2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.
You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

Account settings

On the Account settings step of the workflow, enter details of how you would like to manage accounts with Oracle Access Governance when configured as a managed system:
  1. Select where to send notification emails when an account is created. The default setting is User. You can select one, both, or none of these options. If you select no options then notifications will not be sent when an account is created.
    • User
    • User manager
  2. When an identity moves within your enterprise, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. In some cases the identity will no longer require certain accounts which are not relevant to their new role in the enterprise. You can select what to do with the account when this happens. Select one of the following options:
    • Disable
    • Delete
  3. When an identity leaves your enterprise you should remove access to their accounts. You can select what to do with the account when this happens. Select one of the following options:
    • Disable
    • Delete

Note:

If you do not configure your system as a managed system then this step in the workflow will display but is not enabled. In this case you proceed directly to the Integration settings step of the workflow.

Note:

If your orchestrated system requires dynamic schema discovery, as with the Generic REST and integrations, then only the notification email destination can be set (User, Usermanager) when creating the orchestrated system. You cannot set the disable/delete rules for movers and leavers. To do this you need to create the orchestrated system, and then update the account settings as described in Configure Orchestrated System Account Settings.

Integration settings

On the Integration settings step of the workflow, enter the configuration details required to allow Oracle Access Governance to connect to the IBM DB2 database.

  1. In the Easy Connect URL for Database field, enter the connect string for the database you want to integrate with Oracle Access Governance, in the format host/port/database service/sid.
  2. In the User Name field, enter the IBM DB2 user you will use to connect to the database. This is the user you created in Create a DB2 System User Account for Database User Management (DB2) Orchestrated System Operations.
  3. Enter the password of the IBM DB2 database user in the Password field. Confirm the password in the Confirm password field.
  4. In Connection Properties enter any connection properties in the format prop1=val1#prop2=val2
  5. In Custom Jar Details enter the jar name and the jar checksum in the format <jarName>::<jarChecksum.
    For example:
    db2jcc.jar::c8520f145b428b1133b771bb2c70a6f0f546c9f0655f9de5de2e7b64d5ede786911ad50b543846154fe373dead78d38fb6dded560e0de4c4e8ccbbf0a06b6c1e

    For more information on custom jar support, refer Custom Jar Support.

  6. Check the right hand pane to view What I've selected. If you are happy with the details entered, click Add.

Finish up

On the Finish Up step of the workflow, you are asked to download the agent you will use to interface between Oracle Access Governance and IBM DB2 database. Select the Download link to download the agent zip file to the environment in which the agent will run.

After downloading the agent, follow the instructions explained in the Agent Administration article.

Finally, you are given a choice whether to further configure your orchestrated system before running a data load, or accept the default configuration and initiate a data load. Select one from:
  • Customize before enabling the system for data loads
  • Activate and prepare the data load with the provided defaults

Post Configuration

For DB2 Database system to integrate with Oracle Access Governance, driver jar needs to be registered with the agent. For more information, refer Custom Jar Support.