Invoke an Application's SOAP Endpoint with OAuth

When you configure an invoke connection in an integration, you can use OAuth to securely invoke the SOAP API of an external application. Here's a summary of what you need to configure to use OAuth with SOAP invoke connections in an integration.

When an integration invokes the endpoint of an external application, Oracle Integration requests access from the authorization server for the external application. Once access is granted, Oracle Integration accesses the SOAP endpoint, authenticates with the external authorization server, and invokes the application.


When an integration invokes the SOAP endpoint of an external application, Oracle Integration requests access from the authorization server for the external application. Once access is granted, Oracle Integration accesses the SOAP endpoint, authenticates with the external authorization server, and invokes the application.

Configuration Summary

Is OAuth required? Supported grant types Required roles

No. You can use other authentication types supported by the external application.

Supported OAuth grant types for invoke SOAP Adapter connections:

  • JWT User Assertion
  • Authorization code
  • Client credentials
  • Resource Owner Password Credentials (not recommended)

See About OAuth 2.0 Grants for more details.

If you are calling an external endpoint, the role you assign depends on the external application requirements.