Uploaded September 2026 | Updated November 2026, 5 days ago
Need to invoke Fusion Apps REST APIs from Oracle Integration when the identity domain is not the one for Fusion Apps? This tutorial shows how to configure an OAuth 2.0 Authorization Code connection through a non-Fusion identity domain, such as an Oracle Integration identity domain.
Learn how the three-legged Authorization Code flow establishes the user identity behind the access token and how Fusion Apps authorizes access to its REST APIs. The walkthrough gathers the Fusion Apps host URL, OAuth client details, authorization and access-token URIs, scopes, and the correct Oracle Integration redirect URI.
You will set up trust between Fusion Apps and the non-Fusion identity domain, retrieve the JWK signing-certificate endpoint, configure the confidential client application, enable the Authorization Code and Refresh Token grant types, add the required resource and scope, provide consent, and validate the Oracle Integration adapter connection. It also explains when a matching local user is required in a nonfederated identity domain.
Chapters:
0:00 Understand OAuth with a non-Fusion identity domain
2:08 Gather Oracle Integration connection details
3:11 Configure the correct redirect URI
4:21 Set up trust between Fusion Apps and the identity domain
7:15 Retrieve signing-certificate details
8:26 Configure the confidential client application
9:30 Add grant types, resources, and scopes
11:20 Provide consent and configure the adapter
13:32 Validate the OAuth connection
Key links:
Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain: docs.oracle.com/en/cloud/paas/application-integration/erp-adapter/use-identity-domain-not-included-oracle-fusion-applications.html
Explore more Code Innovate videos: youtube.com/playlist?list=PLPIzp-E1msrZMCfSHbKgLK3KWsNM9JB9a
Related video: How to use Oracle Integration to Power Fusion AI Agents: youtube.com/watch?v=7kjH0uXyUAI&list=PLPIzp-E1msrZMCfSHbKgLK3KWsNM9JB9a&index=26&pp=iAQB
#OAuth #OracleIntegration #FusionApps #IdentityDomain
Who this is for: Oracle Integration developers and identity-domain administrators who need OAuth access to Fusion Apps REST APIs from an identity domain that is not the Fusion Apps identity domain.
Prerequisites: a Fusion Apps host URL, Oracle Integration runtime URL, identity-domain administration access, and an account with the Fusion Apps roles needed by the target REST API.
Key concepts: OAuth 2.0 Authorization Code, three-legged OAuth, non-Fusion identity domain, federation, JWK signing certificates, redirect URI, confidential client application, resource scope, refresh token, and user consent.
By the end: a trusted OAuth connection that Oracle Integration can use to invoke Fusion Apps REST APIs.
#codeinnovate
Need to invoke Fusion Apps REST APIs from Oracle Integration when the identity domain is not the one for Fusion Apps? This tutorial shows how to configure an OAuth 2.0 Authorization Code connection through a non-Fusion identity domain, such as an Oracle Integration identity domain.
Learn how the three-legged Authorization Code flow establishes the user identity behind the access token and how Fusion Apps authorizes access to its REST APIs. The walkthrough gathers the Fusion Apps host URL, OAuth client details, authorization and access-token URIs, scopes, and the correct Oracle Integration redirect URI.
You will set up trust between Fusion Apps and the non-Fusion identity domain, retrieve the JWK signing-certificate endpoint, configure the confidential client application, enable the Authorization Code and Refresh Token grant types, add the required resource and scope, provide consent, and validate the Oracle Integration adapter connection. It also explains when a matching local user is required in a nonfederated identity domain.
Chapters:
0:00 Understand OAuth with a non-Fusion identity domain
2:08 Gather Oracle Integration connection details
3:11 Configure the correct redirect URI
4:21 Set up trust between Fusion Apps and the identity domain
7:15 Retrieve signing-certificate details
8:26 Configure the confidential client application
9:30 Add grant types, resources, and scopes
11:20 Provide consent and configure the adapter
13:32 Validate the OAuth connection
Key links:
Set Up the OAuth Authorization Code Credentials Security Policy with a Non-Oracle Fusion Applications Identity Domain: docs.oracle.com/en/cloud/paas/application-integration/erp-adapter/use-identity-domain-not-included-oracle-fusion-applications.html
Explore more Code Innovate videos: youtube.com/playlist?list=PLPIzp-E1msrZMCfSHbKgLK3KWsNM9JB9a
Related video: How to use Oracle Integration to Power Fusion AI Agents: youtube.com/watch?v=7kjH0uXyUAI&list=PLPIzp-E1msrZMCfSHbKgLK3KWsNM9JB9a&index=26&pp=iAQB
#OAuth #OracleIntegration #FusionApps #IdentityDomain
Who this is for: Oracle Integration developers and identity-domain administrators who need OAuth access to Fusion Apps REST APIs from an identity domain that is not the Fusion Apps identity domain.
Prerequisites: a Fusion Apps host URL, Oracle Integration runtime URL, identity-domain administration access, and an account with the Fusion Apps roles needed by the target REST API.
Key concepts: OAuth 2.0 Authorization Code, three-legged OAuth, non-Fusion identity domain, federation, JWK signing certificates, redirect URI, confidential client application, resource scope, refresh token, and user consent.
By the end: a trusted OAuth connection that Oracle Integration can use to invoke Fusion Apps REST APIs.
#codeinnovate










