SOAP Adapter Restrictions

Note the following SOAP Adapter restrictions.

• Transport Layer Security (TLS) version 1.3 is not supported.
• Two-way SSL is not supported for calls to external services through the connectivity agent. Two-way SSL requires direct connectivity from Oracle Integration without the connectivity agent. 
• You cannot invoke a SOAP endpoint from Oracle Integration that is using SAML-based security. This is by design. The SAML security policy is only supported with trigger connections.
• The SOAP Adapter does not support RPC-style WSDL binding.
• Integrations exposed as SOAP APIs (using a SOAP Adapter-specific connection configured as a trigger) cannot accept attachments.
• Without specifying a header, multiple parts in a document-style WSDL are not supported.
• You cannot switch from an asynchronous trigger/callback invoke to nonasynchronous trigger/invoke.
• NT LAN Manager (NTLM) authentication is not supported.
• SOAP WSDL 1.2 binding is not supported in the inbound direction. That version is only supported in the outbound direction.
• Operation overloading in the WSDL file is not supported with the SOAP Adapter. For example, assume your WSDL file includes the following operations with the same name, but different cases:
  • getDocumentStatus
  • GetDocumentStatus

  Each operation is also using a different request payload.

  If you select the GetDocumentStatus operation in the Adapter Endpoint Configuration Wizard, it is invoked at runtime, but the request payload corresponds to the getDocumentStatus operation. The mapper also shows the payload corresponding to the getDocumentStatus operation. If you change the order in the WSDL and upload it on the Connections page, this leads to activation failure. Oracle recommends the following:

  • Use unique operation names.
  • Comment out the other operation in the uploaded WSDL when creating a connection.