3786890 - Support for Custom WS-Security Headers with STS Integration or Custom Timestamp Signing Algorithms in Cloud Integration SOAP adapter

You want to configure SAP Cloud Integration (CPI) to send custom WS-Security headers containing SAML assertions, integrate with a Security Token Service (STS), or specify a particular signing algorithm for the WS-Security <Timestamp> element.

One or more of the following symptoms may occur:

• The receiving system rejects the SOAP message due to the signature algorithm used for the WS-Security timestamp.
• The receiver expects a signing algorithm other than SHA1 for the <Timestamp> element.
• You need to customize the WS-Security header beyond the standard capabilities provided by the SOAP adapter.
• You require STS-based token acquisition and insertion into the outbound WS-Security header.

• SAP Integration Suite
• SAP Cloud Integration

SAP Cloud Integration, Integration Suite, CPI, SOAP Adapter, WS-Security, WS Security, Security Token Service, STS, SAML Assertion, SAML Token, Timestamp, WS-Security Timestamp, Signature Algorithm, SHA1, SHA-1, SHA256, SOAP Security, SOAP Header, Custom WS-Security Header, Receiver Policy, Security Policy, Timestamp Signature, Digital Signature, XML Signature, WSSE, WSS, SOAP Receiver, Signing Algorithm, Security Header Customization , KBA , LOD-HCI-PI-CON-FTP , FTP, SFTP and SOAP Adapter , Problem