Connect to Oracle Integration APIs
You can connect to Oracle Integration APIs using identity propagation or fixed credentials.
Connect to Oracle Integration APIs Using Identity Propagation
If your environment's Visual Builder instance was provisioned as a part of Oracle Integration, using the Oracle Cloud Account authentication method provides identity propagation from VB Studio to Oracle Integration without any additional configuration. For VB Studio, the Integration backend is copied over from your associated Visual Builder instance and is set to use the Visual Builder proxy.
The Oracle Integration URL and the authentication method are derived from the Tenant Settings of your environment's Visual Builder instance. The URL should be similar to https://<Integration Cloud Instance full URL>:443
and the authentication method should be Oracle Cloud Account. These values then appear as the default URL and authentication method in the visual application's Backends editor from the Navigator's Services tab.
When creating the service connection, you use the following authentication method:
Authentication method | Details |
---|---|
Oracle Cloud Account |
The default authentication for the connection is determined by the authentication set in the visual application's Backends editor and in the Tenant Settings of your environment's Visual Builder instance. You can view the connection details in the Backends editor that you access from the Navigator's Services tab. You can choose to override these inherited settings:
|
To connect to Oracle Integration APIs using identity propagation:
Connect to Oracle Integration APIs Using Fixed Credentials
To connect to Oracle Integration APIs using fixed credentials, you can choose to use either Basic Auth or OAuth 2.0 Resource Owner Password as the authentication method.
To access the Oracle Integration APIs using fixed credentials, the environment's Oracle Integration and Visual Builder instances do not need to be located in the same domain or governed by the same IDCS instance. Configuration is the same in both cases.
When you create the service connection in the Create Service Connection wizard, you choose the service by either selecting it in the Service Catalog or by defining its endpoint or specification. If you want to select a service from the catalog, you will first need to open the Backends tab from the Navigator's Services tab and override the tenant-level settings associated with your environment's Visual Builder instance for Integrations and select the authentication method you want to use instead of the default Oracle Cloud Account method.
You do not need to override the Visual Builder instance's tenant-level settings if you are defining the service connection by endpoint or specification in the Create Service Connection wizard. The authentication methods are the same in both cases.
If you want to use OAuth 2.0 Resource Owner Password as the authentication method, a service administrator needs to perform the following steps in the IDCS instance governing the Oracle Integration instance to get its Client ID, Client Secret, and Scope. These details are not needed when using Basic authentication.
- Open Applications in IDCS and locate the Oracle Integration application which frontends the Integration instance.
- Open the application and copy the Client ID and Client Secret in the General Information panel of the Configuration tab.
- Expand the Resources panel of the Configuration tab and copy the Primary Audience and the scope that corresponds to the REST APIs. These are combined to give the full scope, and might be similar to
https://<primary-audience-unique-id>.integration.ocp.oraclecloud.com:443/ic/api
.
When creating the service connection, you can use either of the following authentication methods:
Authentication method | Details |
---|---|
Basic |
To use this option you need to provide the following details:
|
OAuth 2.0 Resource Owner Password |
To use this option you need to provide the following details:
|
If you do not have access to IDCS, you will need to request the connection details from an administrator if you want to use the OAuth 2.0 Resource Owner Password authentication method.
To connect to Oracle Integration APIs using fixed credentials: