Client IDs for Connect Application in Integration Center
Beginning in Oracle CPQ 25D, the Generic Integrations feature in the Integration Center has been renamed Connected Applications. Connected Applications supports all previously defined generic integrations and adds a new optional Client Id field which can be used with Oracle Identity Cloud integrations.
If your site is currently using Oracle Identity Cloud as your OAuth Provider, you have the option to create a Confidential Application and provide that application’s Client ID to Oracle CPQ. This Client ID will allow you to make system-to-system calls from an external application into Oracle CPQ using OAuth.
Client IDs provide a way for customers to make inbound calls to CPQ securely using OAuth. It also allows customers to connect external applications to CPQ for machine-to-machine communication without requiring a named “integration user” who consumes a user license.
Steps to Enable
Before using this feature, you must have configured an Identity Domain in Oracle Identity and Access Management (IAM, also known as Oracle Identity Cloud) and set it up as an OAuth Provider in the Integration Center. You must also have added your external application as a Confidential Application. Refer Add a Confidential Application for more information.
To configure a IDCS integration as your OAuth provider, complete the following steps:
- Retrieve the Client ID noted when you added a Confidential Application for IDCS.
- Navigate to the Admin Home page in Oracle CPQ.
- Click Integration Center in the Integration Platform section.
- Select Connected Applications in the Type drop-down.
- Enter the name for the integration.
- Enter the URL in the Request URL field.
- (Optional) Enter a description for the integration.
Note: The username and password fields are used only for outbound integrations and are not related to the inbound OAuth flow.
- Enter the Client ID from Step 1.
- Select the Enable Integration checkbox.
- Click Create Integration.
Tips And Considerations
- The username and password fields are used only for outbound integrations and are not related to the inbound OAuth flow.
- Connected Applications using OAuth have unrestricted access to the entire CPQ application and its data in Oracle CPQ 25D. Customers need to limit access to Confidential Applications.
- Connected Applications support Client Credentials grant type.