Prerequisites for Creating a Connection

Subscribe to Oracle ERP Cloud

This action enables you to create an Oracle ERP Cloud user account with the correct privileges. You specify this user account when creating an Oracle ERP Cloud Adapter connection on the Connections page.

See Oracle ERP Cloud.

Verify the Status of Location-Based Access Control (LBAC)

Check if you have enabled Location-Based Access Control (LBAC) for Fusion Applications (for Oracle ERP Cloud).

If LBAC is enabled, you must allowlist (explicitly allow identified entities access) the Oracle Integration NAT Gateway IP address in your LBAC. If you do not perform this task, you can receive a 401 Access Denied error or 403 Forbidden error from Oracle Fusion Applications.

See How Location-Based Access Works in Securing Oracle SCM Cloud and Doc ID 2615294.1 at Oracle Support Services.

Obtain the Oracle ERP Cloud Service Catalog Service WSDL, Event Catalog URL, or Interface Catalog URL (For Connections Created Prior to 2/18/20)

The steps in this section are only required for existing connections created prior to the initial release of the simplified connections page on 2/18/20. For existing connections, you are prompted to specify a service catalog service WSDL (for accessing and configuring the inbound and outbound adapter to use either business objects or business services) in the ERP Services Catalog WSDL URL field and optionally an event catalog URL (for accessing and configuring the inbound adapter to use event subscriptions) in the ERP Events Catalog URL field and interface catalog URL (for accessing and configuring the outbound endpoint using REST business resources) in the Interface Catalog URL field.

Note:

For new connections created with the initial release of the simplified connections page on 2/18/20, the preconfiguration details described in this section are not required. All WSDLs and URLs are automatically identified for you based on the Oracle ERP Cloud host name that you specify in the ERP Cloud Host field on the Connections page.

The following sections describe how to obtain the service catalog service WSDL and event catalog URL:

For Fusion Applications Releases 13 and Later

Obtain the Oracle Fusion Applications Release 13 and later service catalog service WSDLs and event catalog URLs through the following methods.

Obtain the Service Catalog Service WSDL

To obtain the physical endpoint of your instance, perform the following steps:

Log in to the Fusion Applications home page. For example:
```
https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome
```
Where acme is the system name and us6 is the data center.
Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ServiceCatalogService?WSDL. For example:
```
https://acme.fs.us2.oraclecloud.com/fscmService/ServiceCatalogService?WSDL
```

Obtain the Event Catalog URL

Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint. You must switch to the new consolidated endpoint that conforms to the following naming pattern:

https://systemName.fa.dcsn.oraclecloud.com/...

You must switch to the consolidated endpoint immediately after upgrading to Release 13. Newly provisioned instances using Release 13 only have the consolidated endpoint available. In Release 13, multiple domains are consolidated. You must specify the domain in the URL. For example, if specifying the fa domain, the URL looks as follows:

Copy the following URL:
```
https://acme.fa.us6.oraclecloud.com/
```

Append soa-infra to the end of the URL:

https://acme.fa.us6.oraclecloud.com/soa-infra

Assign Required Roles to an Integration User

To use the Oracle ERP Cloud Adapter in an integration, you must assign specific roles to an integration user.

Associating the Integration User with the Following Roles and Privileges

You associate the user with the following roles and privileges.

Role	Description
Integration Specialist	This is a job role and does not include data roles. Assign the Integration Specialist role that inherits Oracle ERP Cloud roles. This role applies to Release 13.
Oracle ERP Cloud-specific data access to the integration user	You must specify the specific data access roles based on the objects you want to integrate. This role applies to Release 13. See Managing Data Access for Users: Explained of Securing Oracle Cloud ERP.
AttachmentsUser	Provides access to the Attachments security group to download the log file or the output file with the ERP Integration Service. This role is automatically shipped. You must verify that this role is automatically assigned to the user.
SOAOperator	The SOA operator role is required to receive ERP business events.
FND_MANAGE_CATALOG_SERVICE_PRIV	The role to manage the web services catalog.
Customer Relationship Management Application Administrator (for Oracle CRM Cloud implementations)	See Chapter Customer Relationship Management Application Administrator (Job Role) in Security Reference for CX Sales and B2B Service.

Additional roles may be required as per each interface requirements.

Using the Security Console

Use the Security Console to manage application security such as roles, users, certificates, and administration tasks. Access to the Security Console is provided by the predefined Security Manager role. Access the Security Console in the following ways:

Use the Manage Job Roles or Manage Duties tasks in the Setup and Maintenance work area.
Select Navigator, then Tools, then Security Console.

Description of the illustration sales_cloud_security.png

See Using the Security Console in Securing Oracle Cloud ERP.

Create Connections Based on the User Role

You can create more than one service integration user account in Oracle Fusion Applications for different Oracle Fusion Applications roles that exist to perform different tasks and then create different Oracle Integration connections using those user accounts.

For example, you can create multiple connections in Oracle Integration such as ERP1, ERP2, ERP3, and so on and associate each of these connections with a designated account in Oracle ERP Cloud, such as user_integration_1 (general ledger), user_integration_2 (HCM), and user_integration_3 (projects). These actions create different connections for invoking different Oracle ERP Cloud jobs using an Oracle Fusion Applications user account set up for that job.

Configure Oracle ERP Cloud for Event Subscriptions

You must create a CSF key or use a token-based authentication scheme to subscribe to events in Oracle ERP Cloud. This key or scheme is required by the event handler framework when it invokes the integration.

Check if the Token-Based Authentication Scheme is Enabled for Event Integrations

The token-based authentication scheme is added in the Oracle ERP Cloud Adapter for business and FBDI event messages originating from Oracle Fusion Applications.

Oracle ERP Cloud Adapter token-based authentication uses time-sensitive session tokens generated using strong encryption on the Oracle Fusion Applications event handler and passed to Oracle Integration. The session token is validated by Oracle Integration against the Oracle ERP Cloud application sender and added to local cache. Tokens are never persisted on Oracle Fusion Applications or Oracle Integration. Token-based authentication is more optimal than a CSF key because:

The token refreshes automatically.
You don’t have to worry about expiration.
It's stronger than a CSF key, where user name and password are compromised, then all gone. Token-based authentication is difficult to compromise because tokens are self-generated.
No additional settings are required.

For token-based authentication, the EHF-Token must be present in the HTTP headers of the event message. In the absence of the EHF-Token, Oracle Integration checks for the CSF key credentials for authentication. Token-based authentication removes the dependency on the CSF entry in Oracle SOA Composer.

The token-based authentication scheme is enabled for event integrations with Oracle Integration if the integration is created or reactivated after the May 2021 release. All event integrations created prior to the May 2021 release continue to use CSF key authentication. The token-based authentication scheme is only enabled for that integration after integration reactivation. No additional configuration steps are required.

After reactivation, the event subscription is automatically enabled. Token-based authentication is applied to the activated endpoint and the Oracle Fusion Applications subscription is updated to use the same scheme in the event request.

A token-based authentication-enabled integration does not require CSF credentials in the event message for authentication. The integration reads the EHF-Token from the request headers in the event message and authenticates it with the error handling framework's token validation service in Oracle Fusion Applications.

For an activated event integration, check the csfKey value in the Subscription entry using the following subscription URL.

Open with Postman.

https://fa_host.oraclecloud.com/soa-infra/PublicEvent/subscriptions

Search the Subscription entry by integration name.
An empty csfKey field in Subscription means the token-based authentication scheme is enabled for the integration. A CSF key is not required.

Create a CSF Key

The credentials of the integration are managed by the CSF key. Create the CSF key in Oracle SOA Composer.

Note:

There is only one SOA instance in Release 13.
The Oracle Integration password may expire periodically. Your application administrator must contact the Oracle Integration administrator to get the refreshed user credentials. The application administrator must update the CSF key when this password is refreshed.

Ensure that you specify the following information correctly when creating the CSF key:

Create the CSF key name. The name must be a combination of the Oracle Identity Cloud Service service ID and the name of the integration instance.
1. Click your username initials in the title bar, then select About.
2. Copy the Identity Domain value (for example, idcs-638a2ce020e60c2881) and the Service Instance value (for example, oic1575).
3. Assemble the CSF key value with the identity domain first and the service instance second (no space in between): idcs-638a2ce020e60c2881oic1575.
Create the CSF key with the Oracle Integration user account with which you log in to Oracle Integration and not the user name created when you subscribed to Oracle ERP Cloud.
Ensure that the CSF key password has not expired.

Log in to Oracle SOA Composer with a user that has the SOA administrator role. Obtain the hostname and port from your administrator.
For example, in Release 13:
```
 https://acme.fa.us6.oraclecloud.com/soa/composer
```
Click Manage Security.
Add the CSF key name. The name must be a combination of the Oracle Identity Cloud Service service ID and the name of the integration instance.
Provide the user name and password that you enter to log in to Oracle Integration. Do not enter the user name and password created when you subscribed to Oracle ERP Cloud.

The Oracle Integration user must exist in Oracle Integration and have been assigned the ServiceUser role.

The CSF key entry in the Oracle ERP Cloud infrastructure stores the Oracle Integration credentials used by Oracle ERP Cloud. When Oracle Fusion Applications send outbound requests to Oracle Integration (at runtime), it sends the credentials (user name and password) of this account for authentication.
Click Register.

Upload Files in Bulk and Insert Data into Oracle ERP Cloud Application Tables for New Integrations

When using an Oracle ERP Cloud Adapter connection in an existing integration, you must satisfy the following prerequisites for the upload of files in bulk and the insertion of data into Oracle ERP Cloud application tables.

Satisfy the following prerequisites for the bulk upload of files and the insertion of data into Oracle ERP Cloud application tables. This is only required for an ERP Cloud callback upon job completion. Only file-based data import (FBDI)-compliant jobs are supported for callbacks.
1. Create a user similar to the Oracle ERP Cloud Adapter connection user in the My Services or Oracle Cloud Infrastructure Console. This user is linked to the Oracle Integration WebLogic security realm. The user name must exactly match the Oracle ERP Cloud user name. The password and email address can be anything. Ensure that this user has permissions to execute integrations in Oracle Integration. It is recommended that you have a role such as ServiceAdmin or ServiceDeveloper, which have executable permissions on integrations. Ensure that you select the Integration role for the Oracle ERP Cloud user in the Oracle ERP Cloud application.
2. Import the following certificates:
  - In your browser, enter the service catalog URL:
    For Release 13:
```
https://hostname:port/fscmService/ServiceCatalogService?WSDL
```
  - In the WSDL, navigate to the X509 certificates section:
    
    Description of the illustration erp_certificates.png
  - Copy the first certificate string to a file.
    Note:
    For each certificate file that you create, add your certificate string between the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines for the certificate to be successfully imported into Oracle Integration. For example:
```
-----BEGIN CERTIFICATE-----
certificate_string
-----END CERTIFICATE-----
```
    Otherwise, you may receive an Invalid Certificate error.
  - Copy the second certificate to a file. You have two certificate files (for example, erp_cert1.cer and erp_cert2.cer).
  - In the Upload Certificate dialog in Oracle Integration, import both certificates as Message Protection Certificate types and enter unique alias names. See Upload a Certificate to Connect with External Services.
  - Satisfy the following manifest file recommendations (that is, the properties file in the zip file that must be uploaded to Universal Content Management (UCM)).
    - The manifest file expects import process details in the following format:
```
<job package name>,<job def name>,<Manifest file name>,<job parameters (comma separated)>
```
      For example:
```
oracle/apps/ess/financials/payables/invoices/transactions,APXIIMPT,AP,#NULL,#NULL,#NULL,#NULL,#NULL,#NULL,#NULL,INVOICE
```
    - The manifest file name should be a prefix of the actual zip file name if it contains _. Otherwise, it should just be the name. For example, if the zip file name is AP_301.zip, the manifest file name should be AP.properties and the third value in the manifest should be the manifest file name. If the zip file name is AP.zip, the manifest file name should be AP.properties and the third value in the manifest should be the manifest file name.
    - Only one job is supported per invoke. You can have multiple entries in the manifest property file to import data from the interface table to the applications tables in batches of up to 10 for sequential or up to 5 for parallel processing. For example, the journal import data file has records of 10 ledgers. The property file has 10 entries with the unique ledger name as a parameter. After the data file is loaded in the interface table, the import process has 10 subprocesses for each ledger.
Satisfy the following prerequisites to configure the integration that uses the bulk import feature:
1. Map the following parameters to the Oracle ERP Cloud Adapter.
  - Map parameter ICSFileReference to the File Reference parameter from the other adapter (for example, the FTP Adapter, the REST Adapter, or whichever adapter you used that has the ICSFileReference parameter).
  - Map the FileName parameter from the source schema to the target schema (the target schema is the Oracle ERP Cloud bulk import schema). The FileName must be unique for every request.

Upload Files to Oracle WebCenter Content

To upload files to Oracle WebCenter Content (Universal Content Manager) with the Oracle ERP Cloud Adapter, you must satisfy the following prerequisites.

Create a PGP Public Key:

To upload encrypted files, a PGP public key is required. You must generate the PGP public key and save it for upload. The supported algorithm for the public key is RSA for encryption and the key size must be 1024 bits in length.

The process for uploading files into Oracle ERP Cloud is:
- You encrypt files using the Oracle ERP Cloud public key.
- The data-loading process decrypts files using the Oracle ERP Cloud private key.
Configure Security and User Access

Once you have configured security groups and doc accounts for the file to upload, you can configure the Oracle ERP Cloud Adapter to upload the file to Oracle WebCenter Content.

See Understanding Security and User Access in Administering Oracle WebCenter Content.

Create Custom Business Events

You can create custom business events in Application Composer that are visible for selection when configuring the Oracle ERP Cloud Adapter as a trigger connection in the Adapter Endpoint Configuration Wizard. You must access Application Composer through the Oracle Fusion Applications user interface. Select ERP and SCM Cloud from the Applications list in Application Composer to create the custom objects and promote them as custom events to be consumed by the Oracle ERP Cloud Adapter.

Note:

Custom business events are supported only for Oracle ERP Cloud custom business objects.

See technical note 2535444.1 at My Oracle Support for instructions.

Access the REST Catalog Through the Oracle ERP Cloud Adapter

You must perform the following steps to access the REST catalog through the Oracle ERP Cloud Adapter. This enables you to browse for REST resources on the Operations page of the Adapter Endpoint Configuration Wizard. This also enables Oracle ERP Cloud to skip REST resources when an error is encountered while generating the metadata. Without this, Oracle ERP Cloud generates a partial catalog that results in missing business resources on the Operations page.

Note:

After saving your profile value changes, it takes approximately 30 minutes for the REST resources to be available for selection in the Adapter Endpoint Configuration Wizard.

Log in to the Cloud Applications Home Page for ERP Financials.
In Setup and Maintenance, open the Task list and click Search.
Enter Manage Profile Option and click the link.
Click + to add a new profile option.

Define a new profile option with the following details.

Element	Description
Profile Option Code	`ORACLE.BC.REST.IGNORECATALOGERRORS`
Profile Display Name	Ignore REST resource catalog errors.
Application	Oracle Middleware Extensions for Applications
Module	Oracle Middleware Extensions for Applications
Description	If a catalog describe action fails for a particular resource, log an error and proceed with other resources.

Click Save and Close.
In the next screen in the Profile Option Levels section, select the Enabled and Updateable check boxes for Site & User.
Click Save and Close.
Go to the Oracle Fusion Applications Home page and navigate to Setup and Maintenance.
Search for the task Manage Administrator Profile Values.
In the Name column, click the Manage Administrator Profile Values task.
In the Profile Option Code field, select ORACLE.BC.REST.IGNORECATALOGERRORS, and click Search.

The search results are displayed.

Description of the illustration search_results.png
Under ORACLE.BC.REST.IGNORECATALOGERROR Profile Values, click + to add a row in the Profile Level section.
Select the Profile Level list to show the following options.
- Site: The ORACLE.BC.REST.IGNORECATALOGERROR profile value is applicable to all users.
- User: The ORACLE.BC.REST.IGNORECATALOGERROR profile value is applicable only to a specific user.
Select an option.
If you select User:
1. Enter a specific user name in the User Name field.
2. Enter true in the Profile Value field.
Click Save and Close.

Perform Prerequisites to Use the OAuth Authorization Code Credentials Security Policy

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.

Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service

Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.
1. 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.
2. Copy the endpoint.
3. Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.
4. 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
```
5. 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.
6. 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
```
Upload the certificates to the Oracle Fusion Applications Security Console.
1. Log in to Oracle Fusion Applications as a user with the IT Security Manager role.
2. In the navigation pane, select Tools, then Security Console.
3. Select API authentication in the left navigation pane.
4. Click Create Oracle API Authentication Provider, then click Edit in the upper right.
5. In the Trusted Issuer field, enter:
```
https://identity.oraclecloud.com
```
6. In the Token Types section, select JWT.
7. Click Save and Close.
8. Click Inbound API Authentication Public Certificates, then click Add New Certificate.
9. Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT).
10. In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save.
11. Repeat these steps to upload the second certificate file.
Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.
1. Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.
2. In the left navigation pane, click Applications, then click Add.
3. Click Confidential Application.
4. On the Details page, provide a name (for example, FA Resource), and click Next.
5. On the Client page, click Next without making changes.
6. On the Resources page, click Configure this application as a resource server now.
7. Optionally update the value in the Access Token Expiration field.
8. Select Is Refresh Token Allowed.
9. 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
```
10. In the Scopes section, click Add.
11. In the Scope field, enter /.
12. In the Description field, enter All.
13. Select Requires Consent.
14. Click Add, then click Next.
15. On the Web Tier Policy and Authorization pages, click Next without making any changes.
16. Click Finish to complete resource application creation.
17. 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 only required if the Oracle Fusion Applications user is not federated with Oracle Identity Cloud Service or whichever identity provider you are using.

Create an Oracle Identity Cloud Service 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 Oracle Identity Cloud Service that is protecting Oracle Integration.	No. You do not need to create the local Oracle Identity Cloud Service Oracle Fusion Applications user. This is because Oracle Identity Cloud Service already has Oracle Fusion Applications users in its repository.
You do not have federation between Oracle Fusion Applications and the Oracle Identity Cloud Service that is protecting Oracle Integration.	Yes. You must create the local Oracle Identity Cloud Service Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.

The Oracle Identity Cloud Service administrator must create a nonfederated local username in Oracle Identity Cloud Service 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 Oracle Identity Cloud Service and have a local user password.

Create the Confidential Client Application for Oracle Integration

Sign in as the Oracle Identity Cloud Service administrator to the Oracle Cloud Infrastructure Console. This administrator must have Oracle Identity Cloud Service instance access.
In the left navigation pane, select Applications, then click Add to add a client application.
Select Confidential Application.
The Add Confidential Application wizard is displayed.
On the Details page, enter an application name, and click Next.
On the Client page, click Configure this application as a client now.
In the Authorization section, select Refresh Token and Authorization Code.

In the Redirect URL field, enter your Oracle Integration instance URL. 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 to Oracle Integration 3.
The complete instance URL with the region included (required for new instances).

For Connections… Include the Region as Part of the Redirect URL? Example of Redirect URL to Specify…

For Connections…	Include the Region as Part of the Redirect URL?	Example of Redirect URL to Specify…
Created on new Oracle Integration 3 instances	Yes.	`https://OIC_instance_URL.region.ocp.oraclecloud.com/icsapis/agent/oauth/callback`
Created on instances upgraded from Oracle Integration Generation 2 to Oracle Integration 3	No. This applies to both: New connections created after the upgrade Existing connections that were part of the upgrade	`https://OIC_instance_URL.ocp.oraclecloud.com/icsapis/agent/oauth/callback`

Created on new Oracle Integration 3 instances

Yes.

https://OIC_instance_URL.region.ocp.oraclecloud.com/icsapis/agent/oauth/callback

Created on instances upgraded from Oracle Integration Generation 2 to Oracle Integration 3

No.

This applies to both:

New connections created after the upgrade
Existing connections that were part of the upgrade

https://OIC_instance_URL.ocp.oraclecloud.com/icsapis/agent/oauth/callback

For the OAuth authorization code to work, the redirect URI must be set properly.

Under Resources, click Add Scope to add appropriate scopes.
If the Oracle Fusion Applications instance is federated with the Oracle Identity Cloud Service instance, the Oracle Integration cloud service application is listed among the resources for selection. This enables the client application to access Oracle Integration.
Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service.
Select the resource and click >.
Select the scope, then click Add.
Click Next without making changes on the Resource and Web Tier Policy pages.
On the Authorization page, click Finish.
The Application Added dialog shows the client ID and client secret values.

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.

If The...	Then...
Oracle Identity Cloud Service 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.
Oracle Identity Cloud Services 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 Oracle Identity Cloud Service application using the local Oracle Fusion Applications user account created earlier.

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.

Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.
Return to the Connections page and retest the connection.
The connection is successful this time.