1. Integrating Fusion Service with Field Service
  2. Create Integration Services Access for Connecting to Oracle Integration

Create Integration Services Access for Connecting to Oracle Integration

To use the Oracle Integration-(OIC) based integration, the credentials for the integration user created in Oracle Integration must be stored in Oracle Field Service.

The integration between OIC and Oracle Field Service is supported by the OAuth 2.0 Authentication mechanism.

Navigate to Oracle Field Service Configuration.

To create the connection to OIC, click on Application in the Subsystems section.

Click Add Application.

The following table shows the values you need for the connection:

Field

Description

IDCS URL

 Base URL of your Identity Service Admin Console

Example : https://example.identity.oraclecloud.com
Client ID Client ID of the Client application that you have created in IDCS
Client Secret Client Secret of the Client application that you have created in IDCS.
Scope Scope of the Client application that you have created in IDCS.

Example: https://applicationid.integration.ocp.oraclecloud.com:443urn:opc:resource:consumer::allapplication id is the id of the application created in IDCS.
Private Key Private Key used to configure the IDCS Application.
Key ID Key used to verify the signature in IDCS.

Changing the OIC Application with Basic Authentication to OAuth2.0 Based Authentication:

For OIC applications with Basic Auth configurations, there's a provision to switch to OAuth 2.0 from the Modify Application page. You can choose the authentication type through the Modify Application page and provide the additional details before saving the application update.

Test Connection for OIC Applications:

The Test Connection button is available in the Add/Modify application page to validate the details provided by the user.

Status of the Event Flow:

  • If any event flow fails for OIC applications, the corresponding message is displayed in the application card.
    • HTTP STATUS 401 - Authentication Failed. Please check credentials.
    • HTTP STATUS 403 - Provided user is not authorized.
    • HTTP STATUS 404 - Host unreachable. Please check your credentials.
    • HTTP STATUS 500 - Connection failed. Please try again later.
Note: Make sure you have configured all the prerequisites for "JWT User Assertion" based authentication as per this documentation: Prerequisites for JWT User Assertion (Visit this site: https://docs.oracle.com/en/cloud/paas/integration-cloud/rest-adapter/authentication-support.html#GUID-33BDEC15-CEC5-4535-8C71-FBA1A37BD7A3). While creating a new Oracle Integration application, Oracle Field Service supports only OAuth 2.0 based authentication. Applications with Basic authentication can still continue with current configurations, or can switch to OAuth 2.0 by selecting the option from the user interface. Once you select OAuth 2.0 you cannot go back to Basic authentication.

Dialog Box to New Page

While creating a new application, you will see a new page with the option to add the configuration details of the application.

This feature provides the ability to test the connection between Oracle Field Service and Oracle Integration with a single click. This helps to ensure that the connectivity is established. In addition, it shows the end point details of a new connection in a full-screen, which provides more real estate for the application.

Related Topics