Authenticating Application End-Users
Applications
There are multiple ways of using IDCS to integrate users and applications within OCI. The method used is mainly dependent on the degree of existing protocols and integration within the application itself.
-
IDCS App Catalog: If the application is one of Oracle’s enterprise applications, or one of many major 3rd party applications (including Salesforce, Adobe, Informatica, Dropbox, SAP, AWS and many more), then Oracle provides a template to enable the application to be integrated for identity and authentication using IDCS. This is the fastest and easiest way to integrate such an application and, if a suitable template exists, the recommendation is to use it.
-
SAML, OAuth, OpenID: If no template exists in the IDCS App Catalog for a given application, but it does support SAML, OAuth or OpenID, then you can add and configure the application for integration with IDCS using those protocols.
-
IDCS App Gateway: If an application is not in the IDCS App Catalog and does not support SAML< OAuth or OpenID integration, the IDCS App Gateway can be used to implement IDCS authentication. The App Gateway intercepts HTTP requests made to the application and ensures that user credentials are correctly supplied to IDCS before forwarding the request to the application.
-
Custom Applications: For new or custom applications, developers can use IDCS’s programming libraries in the application source code, and then recompile and redeploy the application. SDKs are available for programming languages such as Java, Node.js, and Python.
-
Secure Form Fill: With Secure Form Fill, Oracle Identity Cloud Service can automatically fill out the sign-in form and submit the credentials using a browser plugin if your application doesn’t support OAuth, SAML, or any other federated sign-on method.