Overview of Identity Providers

This topic provides an overview of setting up and managing Oracle Identity Cloud Service (IDCS) as an identity provider for managing user signon and authentication.

You can use third party identity providers, such as Active Directory, or you can use Oracle Identity Cloud Service (IDCS). These topics relate to IDCS.

You will need to:

Enable IDCS as your identity provider. See Enabling an Oracle Identity Domain as an Identity Provider.
Set up an identity domain application as an identity provider. See Providing an Identity Domain Application URL for an Identity Provider.
Reference the identity domain application from your Permitting and Licensing implementation. See Providing an Identity Domain Application URL for an Identity Provider and Providing Identity Domain Credentials for Identity Provider.

Important: Currently, there are other steps that must be completed by the Oracle Team within your pods to ensure all internal configurations are in place. Contact Oracle Support for assistance.

When configuring Permitting and Licensing to use IDCS, consider the following:

If you are currently using IDCS as your identity provider using the hybridized instance of IDCS, you just need to enable the feature in Fusion Setup Manager.
If you are adopting IDCS as an identity provider beginning with Update 23D, you will need to perform all the steps on a non-hybridized instance of IDCS.

The hybridized instance of IDCS is the instance that is delivered with Permitting and Licensing for managing roles and authentication between the delivered components, such as OCI Process Automation for workflow.

A non-hybridized instance of IDCS would be the instance you add as a separate instance to be used primarily as an identity provider.

Also, for the hybridized instance of IDCS and Permitting and Licensing, you will need to configure a similar setup for keeping roles synchronized between, for example, Security Console and IDCS. See Creating an Identity Domain Application for Role Synchronization.