Oracle Cloud Infrastructure Documentation

Configure Integration with Oracle Infinity

You can establish a connection between Oracle Access Governance and Oracle Infinity application as a Managed System. To configure, use Orchestrated Systems in the Oracle Access Governance Console.

Prerequisites

Before you install and configure a Oracle Infinity orchestrated system, you should consider the following prerequisites and tasks.

  • You must have an existing active connection with Oracle Cloud Infrastructure for your Oracle Access Governance service instance.
  • Oracle Cloud Infrastructure and Oracle Infinity must reside within the same tenancy and domain.

Create an Integrated SAML Type Application

To create an integrated application of SAML type in OCI IAM, you must have the Identity Domain Administrator role.

You must create a SAML application in OCI IAM to enable Single Sign-On (SSO) integration between your OCI IAM identity provider and the Oracle Infinity product.

  1. Navigate to Identity & Security, and click Domains.
  2. Select Domains.
  3. Click the Integrated applications tab.
  4. Click Add application.
  5. Select SAML Application tile, and then click Launch workflow.
  6. Enter a name for your application, for example, " Infinity SSO".
  7. In the Application URL field, enter https://app.infinitycloud.com.
  8. Click Next.
  9. In the General section, enter the following:
    1. Entity ID: If using OCI IAM as your identity proivder, enter the OCI IAM Domain URL followed by /fed.
    2. Assertion Consumer Service URL: Enter the OCI IAM Domain URL followed by /fed/v1/sp/sso
    3. NameID Format: Unspecified
    4. NameID Value: Username
    5. Upload the signing certificate.
    Use a certificate issued by a trusted Certificate Authority (CA). To create a certificate, refer the steps as explained in Creating a Certificate in OCI IAM.
Additional configurations
  1. In the Signed SSO list, select Assertion.
  2. Select Include Signing Certificate in Signature
  3. Select hashing algorithm, such as SHA-256.
  4. Configure the logout requests as you need.
Attribute Configuration
  1. Configure the following user attributes:
    OptionDescription
    User Name
    • Name: userid
    • Format: Basic
    • Type: User attribute
    • Type value: User Name
    email
    • Name: email
    • Format: Basic
    • Type: User attribute
    • Type value: Primary email
    firstname
    • Name: firstname
    • Format: Basic
    • Type: User attribute
    • Type value: First Name
    lastname
    • Name: lastname
    • Format: Basic
    • Type: User attribute
    • Type value: Last Name
  2. Click Finish.
  3. At the top, select download identity provider metadata. Send the metadata file to your Oracle support team contact.

Configure

You can establish a connection between Oracle Infinity 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. Select 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 Oracle Infinity .
  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. For this orchestrated system, Oracle Access Governance can manage permissions
  4. Click Next.

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

Manage account settings when setting up your orchestrated system including notification settings, and default actions when an identity moves or leaves your organization.

  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, the account is be created if it doesn't exist, when a permission is requested. If the option is cleared, 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 is failed.
  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 is not sent when an account is created.
    • User
    • User manager
  3. When an identity leaves your enterprise you must 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

    These options are displayed only if supported in the orchestrated system type being configured. For example, if Delete isn't supported, then Disable and No action options are displayed.
  4. When all permissions for an account are removed, for example when moving from one department to another, you might 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

    These options are displayed only if supported in the orchestrated system type being configured. For example, if Delete isn't supported, then Disable and No action options are displayed.
  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 reconciles accounts in the managed system and allows to manage them from Oracle Access Governance.

Integration settings

Enter details of the connection to your Oracle Infinity system.

  1. On the Integration settings step of the workflow, enter the details required to allow Oracle Access Governance to connect to your Oracle Infinity system and then click Add.
    Integration settings
    Parameter Name Description
    OCI Orchestrated System Select the dependent OCI orchestrated system name in the list. Your OCI orchestrated system must be Active.
    Infinity-oci
    Domain name Enter the Identity domain name where you have the Oracle Infinity application instance running. For example, Default.
    Oracle Infinity Oracle cloud service name Enter the service name for the Oracle Infinity application running on the Oracle cloud services.
    oracle-infinity
  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.

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 an Oracle Infinity system.