Configure Integration with Database User Management (PostgreSQL)

Prerequisites

Before you install and configure a Database User Management (PostgreSQL) Orchestrated System, you should consider the following prerequisites and tasks.

Certification

  1. Check that your Database User Management (PostgreSQL) system is certified with Oracle Access Governance by referring to Components Certified for Integration with Oracle Access Governance for details of the versions supported.

Create a Service User Account

Oracle Access Governance requires a user account to access the Database User Management (PostgreSQL) system during service operations. Depending on the system you are using, you can create the user in your managed system and assign specific roles and privileges to the user.

Create a Service User Account for Orchestrated System Operations in Database User Management (PostgreSQL)

For Database User Management (PostgreSQL):

  1. Create a user svc_user_admintest using the following query:
    CREATE ROLE "svc_user_admintest" WITH LOGIN PASSWORD 'SecurePass123' CREATEROLE SUPERUSER
CREATEDB REPLICATION BYPASSRLS;
  2. Assign the following roles and privileges to the created user using the following query:
    GRANT pg_read_all_data TO "svc_user_admintest" WITH ADMIN OPTION;
GRANT SELECT ON pg_user TO "svc_user_admintest" WITH GRANT OPTION;

Configure

You can establish a connection between Database User Management (PostgreSQL) and Oracle Access Governance by entering connection details. To achieve this, use the orchestrated systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

The Orchestrated Systems page of the Oracle Access Governance Console is where you start configuration of your orchestrated system.

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 system you would like to integrate with Oracle Access Governance.

You can search for the required system by name using the Search field.

  1. Select Database User Management (PostgreSQL).
  2. Click Next.

Add details

Add details such as name, description, and configuration mode.

On the Add 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 Name field.
  2. Enter a description for the system in the Description 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 Unselected.
  4. Click Next.

Note:

The Database User Management (PostgreSQL) orchestrated system allows you to manage groups in Database User Management (PostgreSQL) using the I want to manage identity collections for this orchestrated system option. If selected, this checkbox allows you to manage Database User Management (PostgreSQL) groups from within Oracle Access Governance. Any changes made to Database User Management (PostgreSQL) groups will be reconciled between Oracle Access Governance and the orchestrated system. Similarly, any changes made in Database User Management (PostgreSQL), will be reflected in Oracle Access Governance

Add Owners

Add primary and additional owners to your orchestrated system to allow them to manage resources.

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

Outline details of how to manage account settings when setting up your orchestrated system including notification settings, and default actions when an identity moves or leaves your organization.

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 to allow Oracle Access Governance to create new accounts when a permission is requested, if the account does not already exist. By default this option is selected meaning that an account will be created if it does not exist, when a permission is requested. If the option is unselected then permissions can only be provisioned where the account already exists in the orchestrated system. If permission is requested where no user exists then the provisioning operation will fail.
  2. Select where and who 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
  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:
    • Delete
    • Disable
    • No action

    Note:

    The options above are only displayed if supported in the orchestrated system type being configured. For example, if Delete is not supported, then you will only see the Disable and No action options.
  4. When all permissions for an account are removed, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. You can select what to do with the account when this happens. Select one of the following options:
    • Delete
    • Disable
    • No action

    Note:

    The options above are only displayed if supported in the orchestrated system type being configured. For example, if Delete is not supported, then you will only see the Disable and No action options.
  5. If you want Oracle Access Governance to manage accounts created directly in the orchestrated system you can select the Manage accounts that are not created by Access Governance option. This will reconcile accounts created in the managed system and will allow you to manage them from Oracle Access Governance.

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 Database Application Tables 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

Enter details of the connection to your Database User Management (PostgreSQL) system.

  1. On the Integration settings step of the workflow, enter the details required to allow Oracle Access Governance to connect to your Database User Management (PostgreSQL) system.

    Table - Integration settings

    Parameter Name Mandatory? Description
    What is the easy connect url for database? Yes Enter the connect string for the database you want to integrate with Oracle Access Governance, in the format jdbc:postgresql:@[host]:[port]:[sid], for example jdbc:postgresql://10.10.20.210:5432/postgres.
    What is the username? Yes Enter the Database User Management (PostgreSQL) user you will use to connect to the database.

    This is the user you created in Create a Service User Account.

    What is the password? Yes Enter the password of the Database User Management (PostgreSQL) user.
    Confirm password Yes Confirm the password.
    What are the custom jar details? Yes Enter the jar name and the jar checksum in the following format <jarName>::<jarChecksum>.

    For example:

    postgresql-42.7.5.jar::ef576afb1d8aa6f28e885ddbc6e5ed7623123b0a151e43e39b52ec0604144def2c310002d8837230cc3eef39f758dea36af1b12984ec6e510b52f8f50b66d05e

    For more information on custom jar, see Custom Jar Support.

  2. Click Add to create the orchestrated system.

Finish Up

Finish up configuration of your orchestrated system by providing details of whether to perform further customization, or activate and run a data load.

The final step of the workflow is 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 SAP User Management (UM). 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.

Pre-Startup Configuration for Agent Initialization

Before starting the agent, ensure that you have added the custom JAR to the agent and completed the following configurations in the config.json and config.properties files:

To add custom JAR:

  1. Navigate to the custom JAR folder.

    <AGENT_HOME>/<PERSISTENT_VOLUME_LOCATION>/data/customJars

  2. Add the postgresql-42.7.5.jar JAR file.

For config.json:

  1. Navigate to the default location of the config.json file.

    <AGENT_HOME>/<PERSISTENT_VOLUME_LOCATION>/data/conf/config.json

  2. Update the following property:

    "numberOfOperationsWorkerThread": 1,

For config.properties:

  1. Navigate to the default location of the config.properties file.

    <AGENT_HOME>/<PERSISTENT_VOLUME_LOCATION>/data/conf/config.properties

  2. Update the following property:

    idoConfig.numberOfOperationsWorkerThread=1

After updating the configuration files, you can start the agent.

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

There are no post configuration steps associated with a Database User Management (PostgreSQL) system.