Prepare to Configure Single Sign-on
Before you configure single sign-on between Oracle Integration and Oracle Fusion Applications, you must gather data from your Oracle Identity Cloud Service instance to file a support request to configure single sign-on for Oracle Fusion Applications.
Before You Begin
Before you begin configuring Oracle Fusion Applications to work with Oracle Identity Cloud Service, ensure you have the following items:
-
An Oracle Identity Cloud Service account with authorization rights to manage apps and users (Identity Domain Administrator or Application Administrator).
-
The identity provider metadata. Modify this URL with the name of your Oracle Identity Cloud Service instance to access the metadata:
https://<IDCS-Service-Instance>.identity.oraclecloud.com/fed/v1/metadata
-
An Oracle Fusion Applications service account with the role
ORA_FND_IT_SECURITY_MANAGER_JOB
to manage the user accounts in Oracle Fusion Applications through Oracle Identity Cloud Service. - The tenant name and domain name. You can get these from your Oracle Fusion Applications environment URL. For example, in the URL
https://jsmith.hcm.example.com/hcmCore
, the tenant name isjsmith
and the domain isexample.com
Get the Fusion Applications Server Data
Before you enable provisioning, you must get the host name and port number for the Oracle Fusion Applications server and use them to establish a connection with Oracle Fusion Applications.
- Log in to Oracle Fusion Applications as an administrator.
- Click Navigator, and then select Setup and Maintenance.
- Click Tasks, and then select Review Topology.
- Click the Detailed tab, and then expand the hcmdomain domain name.
- Note the external server host name and port number values for HCM Core Setup.
Configure Single Sign-on for Oracle Fusion Applications
Before you configure Oracle Fusion Applications in Oracle Identity Cloud Service:
- Go to Oracle Support.
- File a service request to Oracle Support to get the PEM certification from Oracle Fusion Applications Support team.
Metadata.xml
file to the Fusion Apps Support team so that they can import or create an identity provider connector on the Oracle Fusion Applications side.