text
stringlengths 65
20k
|
|---|
u.Click Finish to complete resource application creation.Chapter 2 Prerequisites for Creating a Connection 2-10v.Click Activate to activate your client application.The resource server representing the resource is now active.(Optional) Create a Local User Note: The following step is required if the Oracle Fusion Applications user is not federated with an identity domain or whichever identity provider you are using.1.Create an identity domain local user.Carefully review the following table to see if you already have a local user.Scenario Do I Need to Create a Local User?You have an Oracle Fusion Applications user federated with the identity domain that is protecting Oracle Integration.No.You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console. |
The resource server representing the resource is now active.(Optional) Create a Local User Note: The following step is required if the Oracle Fusion Applications user is not federated with an identity domain or whichever identity provider you are using.1.Create an identity domain local user.Carefully review the following table to see if you already have a local user.Scenario Do I Need to Create a Local User?You have an Oracle Fusion Applications user federated with the identity domain that is protecting Oracle Integration.No.You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security . |
(Optional) Create a Local User Note: The following step is required if the Oracle Fusion Applications user is not federated with an identity domain or whichever identity provider you are using.1.Create an identity domain local user.Carefully review the following table to see if you already have a local user.Scenario Do I Need to Create a Local User?You have an Oracle Fusion Applications user federated with the identity domain that is protecting Oracle Integration.No.You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains . |
1.Create an identity domain local user.Carefully review the following table to see if you already have a local user.Scenario Do I Need to Create a Local User?You have an Oracle Fusion Applications user federated with the identity domain that is protecting Oracle Integration.No.You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment. |
Carefully review the following table to see if you already have a local user.Scenario Do I Need to Create a Local User?You have an Oracle Fusion Applications user federated with the identity domain that is protecting Oracle Integration.No.You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain. |
Scenario Do I Need to Create a Local User?You have an Oracle Fusion Applications user federated with the identity domain that is protecting Oracle Integration.No.You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications . |
You have an Oracle Fusion Applications user federated with the identity domain that is protecting Oracle Integration.No.You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application . |
You do not need to create the local identity domain Oracle Fusion Applications user.This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow . |
This is because identity domain already has Oracle Fusion Applications users in its repository.You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name. |
You do not have federation between Oracle Fusion Applications and the identity domain that is protecting Oracle Integration.Yes.You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored. |
You must create the local identity domain Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next . |
The identity domain administrator must create a nonfederated local username in the identity domain that matches the user in Oracle Fusion Applications.If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now . |
If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications.This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section. |
This user must be created in the identity domain and have a local user password.Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application. |
Create the Confidential Client Application for Oracle Integration 1.Sign in as the identity domain administrator to the Oracle Cloud Infrastructure Console.2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code. |
2.In the navigation pane, click Identity & Security .3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs. |
3.Click Domains .4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues. |
4.Select your compartment.5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2. |
5.Click the identity domain.6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances). |
6.In the navigation pane, click Integrated applications .7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes. |
7.Click Add application .8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud. |
8.Select Confidential Application , then click Launch workflow .9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No. |
9.Enter a name.The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly. |
The remaining fields on this page are optional and can be ignored.10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes. |
10.Click Next .11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection. |
11.In the Client configuration box, select Configure this application as a client now .12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration. |
12.For authorization code, select Refresh token and Authorization code in the Allowed grant types section.13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain . |
13.In the Redirect URL field, enter the redirect URL of the client application.After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >. |
After user login, this URL is redirected to with the authorization code.You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add. |
You can specify multiple redirectChapter 2 Prerequisites for Creating a Connection 2-11URLs.This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages. |
This is useful for development environments in which you have multiple instances, but only one client application due to licensing issues.For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish . |
For example: Note: If you don't know the following information, check with your administrator: If your instance is new or upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2.The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values. |
The complete instance URL with the region included (required for new instances).For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values. |
For ConnectionsInclude the Region as Part of the Redirect URL?Example of Redirect URL to Specify Created on new Oracle Integration Generation 2 instancesYes.https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page. |
https:// OIC_instance_URL .region .ocp.oraclecloud.com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then... |
com/icsapis/agent/oauth/callback Created on instances upgraded from Oracle Integration Generation 2 Generation 2 to Oracle Integration Generation 2No.This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier. |
This applies to both: New connections created after the upgrade Existing connections that were part of the upgradehttps:// OIC_instance_URL .ocp.oraclecloud.com/ icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed. |
14.Under Resources , click Add Scope to add appropriate scopes.If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page. |
If the Oracle Fusion Applications instance is federated with the identity domain, the Oracle Integration cloud service application is listed among the resources for selection.This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier. |
This enables the client application to access Oracle Integration.15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application. |
15.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and an Identity Domain .16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection. |
16.Select the resource and click >.17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful. |
17.Select the scope, then click Add.18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error. |
18.Click Next without making changes on the Resource and Web Tier Policy pages.19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications. |
19.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications. |
The Application Added dialog shows the client ID and client secret values.20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection. |
20.Copy and save these values.You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time. |
You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy. |
Note the following details for successfully authenticating your account on the Connections page.Chapter 2 Prerequisites for Creating a Connection 2-12If The... Then...Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page. |
Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier.You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service. |
You must create a connection and click Provide Consent on the Connections page for authentication to succeed.Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions. |
Identity domain safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page.You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain . |
You need to log in to the Oracle Fusion Applications resource identity domain application using the local Oracle Fusion Applications user account created earlier.21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator. |
21.Activate the application.Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration. |
Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint. |
If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful.However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service . |
However, when you test the connection, it fails with an Unauthorized 401 error.This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint. |
This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu. |
1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs. |
2.Return to the Connections page and retest the connection.The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates. |
The connection is successful this time.Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided. |
Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy.Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format . |
Once these tasks are completed, you can successfully configure a connection on the Connections page.Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files. |
Note: The following instructions apply only to cloud tenancies that still use Oracle Identity Cloud Service.Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate . |
Most cloud tenancies have been migrated to identity domains, which require different configuration instructions.See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate .. |
See Set Up the OAuth Authorization Code Credentials Security Policy with the Oracle Fusion Applications Identity Domain or Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain .If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ... |
If you are unsure of your environment, check with your administrator.Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate .... |
Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service Create the Confidential Client Application for Oracle IntegrationChapter 2 Prerequisites for Creating a Connection 2-13(Optional) Create a Local User Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service 1.Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ..... |
a.Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint.For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ...... |
For example: /admin/v1/SigningCert/jwk See All REST Endpoints in REST API for Oracle Identity Cloud Service .b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate. |
b.Copy the endpoint.c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console. |
c.Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role. |
d.Add that URL to the front of the signing certificate and use a tool (for example, postman ) to invoke the REST APIs.For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console . |
For example: https:// IDCS_URL .identity.oraclecloud.com/admin/v1/SigningCert/jwk e.Perform a GET call to retrieve the payloads of the certificates.There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane. |
There are two sections in the payload: Oracle Identity Cloud Service certificate Certificate authority (CA) certificate Examples of the type of response you receive are provided.See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT . |
See Retrieve the Tenant's Signing Certificate in JWK Format .f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close . |
f.Copy both certificate sections into separate files.Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate . |
Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications: -----BEGIN CERTIFICATE----- content_of_certificate ......-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ). |
.....-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save . |
....-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file. |
...-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource. |
..-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator. |
.-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add. |
-----END CERTIFICATE----- You can validate the certificate.For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application . |
For example: openssl x509 -in IDCS.cert -noout -text 2.Upload the certificates to the Oracle Fusion Applications Security Console.a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next . |
a.Log in to Oracle Fusion Applications as a user with the IT Security Manager role.b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes. |
b.In the navigation pane, select Tools , then Security Console .c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now . |
c.Select API authentication in the left navigation pane.d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field. |
d.Click Create Oracle API Authentication Provider , then click Edit in the upper right.Chapter 2 Prerequisites for Creating a Connection 2-14e.In the Trusted Issuer field, enter: https://identity.oraclecloud.com f.In the Token Types section, select JWT .g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed . |
g.Click Save and Close .h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port. |
h.Click Inbound API Authentication Public Certificates , then click Add New Certificate .i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed. |
i.Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT ).j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add. |
j.In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save .k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears. |
k.Repeat these steps to upload the second certificate file.3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears.k.In the Scope field, enter /. |
3.Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears.k.In the Scope field, enter /.l.In the Display Name field, enter a display name. |
a.Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears.k.In the Scope field, enter /.l.In the Display Name field, enter a display name.m.In the Description field, enter All. |
b.In the left navigation pane, click Applications , then click Add.c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears.k.In the Scope field, enter /.l.In the Display Name field, enter a display name.m.In the Description field, enter All.n.Select Requires Consent . |
c.Click Confidential Application .d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears.k.In the Scope field, enter /.l.In the Display Name field, enter a display name.m.In the Description field, enter All.n.Select Requires Consent .o.Click Add. |
d.On the Details page, provide a name (for example, FA Resource ), and click Next .e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears.k.In the Scope field, enter /.l.In the Display Name field, enter a display name.m.In the Description field, enter All.n.Select Requires Consent .o.Click Add.p.Click Next to move to the next page in the wizard. |
e.On the Client page, click Next without making changes.f.On the Resources page, click Configure this application as a resource server now .g.Optionally update the value in the Access Token Expiration field.h.Select Is Refresh Token Allowed .i.In the Primary Audience field, add the Oracle Fusion Applications URL and port.This is the primary recipient where the token is processed.https:// FA_URL :443 j.In the Scopes section, click Add.The Add Scope dialog appears.k.In the Scope field, enter /.l.In the Display Name field, enter a display name.m.In the Description field, enter All.n.Select Requires Consent .o.Click Add.p.Click Next to move to the next page in the wizard.q.On the Web Tier Policy page, click Next without making any changes. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.