Integrate with Generic REST (Standard UI-driven)

Use Generic REST when you don't have a direct end-to-end connector but have REST APIs for identities (users/accounts) and entitlements (permissions/groups). It ensures onboarding and lifecycle management as the schema, request, response, and test templates are configured directly in Oracle Access Governance and validated at the onboarding time.

Generic REST (Standard UI-driven) Orchestrated System supports the capabilities:

• Onboard any REST-based identity-aware application
• Full data load for Managed Systems
• Manage accounts, and entitlements (permissions)
• Configure request/response templates and authentication in the Console
• Validate schemas and APIs during onboarding
• Support provisioning and reconciliation operations
• Import initial data using flat files when APIs aren't available

The UI-driven Generic REST uses the following setup sequence.

1. Configure Orchestrated System using the Oracle Access Governance Console
   • Create the Generic REST (Standard UI-driven) orchestrated system
   • Configure credentials manually or store them using the OCI vault secret.
   • You can either use flat file for the full data load or configure listing APIs.
   • At this stage, no permissions, lookups, or account schema are defined, and the connection isn't Active.

     See Configure Integration with Generic REST (Standard UI-driven).

2. Define Permissions

   Define permissions to represent entitlements or accesses in the target system. The default attributes are uid and name. Based on the orchestrated system configuration, you can load data either from flat file or use REST APIs. These permissions can be used in an access bundle to enable provisioning and reconciliation operations. See Create Permissions for the Generic REST System.

3. Define Lookups

   Define lookups to manage reference data, such as countries or languages. Based on the orchestrated system configuration, lookup data can be loaded using flat files or REST APIs.

   You can also upload a static file for lookup values instead of configuring REST APIs. In this case, dynamic lookup reconciliation is not supported. See Manage Lookups.

4. Define Account Attributes

   Define the account schema for the system. You can create account attributes manually, or import an account schema file. See Define Account Attributes

5. Configure authentication and connectivity APIs

   Define REST APIs required to establish connectivity with the target system.

   • Configure a Bearer Token API when Bearer authentication is selected. This ensures Authentication is configured correctly. For Basic authentication, no token API is required. See Configure Authentication - For Bearer Token.
   • Configure a Test Connection API to validate connectivity. This ensures that the target REST endpoint is reachable.
6. Define REST APIs for entities required for account lifecycle

   Configure APIs for operations, such as create account, update account, delete account, enable or disable account, get account details and list accounts. For each API, you configure Endpoint URL, Headers and parameters, request body and response. See Configure REST APIs for Entities.

7. Activate orchestrated system.
8. Configure outbound transformation to map identity attributes to account attributes for provisioning operations. See Apply Outbound Transformations for Identity Attributes.

Use Generic REST (Standard UI-driven) to onboard REST-based applications and manage accounts and entitlements without building or maintaining custom connectors.

A logistics company uses several cloud applications that expose REST APIs for managing users, accounts, groups, and access, There is no centralized governance as identity data is manually entered and access is managed using custom scripts or spreadsheets.

Use Generic REST (Standard UI-driven) to onboard all applications using a single, standardized integration model.

• Access Control
  The Generic REST Orchestrated System manages access control through identity collections, roles, access bundles, and Oracle Access Governance policies. Depending on the orchestrated system being used, you can manage access using Oracle Access Governance self service features, specifically Request Access. For example, you can use the Generic REST Orchestrated System:

  • Create New Accounts
  • Reconcile Accounts
  • Update Accounts
  • Disable/Enable Accounts
  • Delete Accounts
  • Add or Remove Permissions

  As new users are added to or removed from specific roles, they automatically gain corresponding access in the systems covered by the Oracle Access Governance policy.