WS-Security SOAP Header does not include expected elements

369 Views

Our SAP R/3 Enterprise is sending messages to XI which then forwards them to third party applications withing our corporate firewall.

One of these applications (Java) provides a Web Service to which we are attempting to direct a message from XI.

This Web Service requires WS-Security information be included in the SOAP header identifying Username, Password as described by the Oasis standards.

<soapenv:Header>

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"

soapenv:mustUnderstand="1">

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"

wsu:Id="UsernameToken-21280292">

<wsse:Username>test</wsse:Username>

<wsse:Password

Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"

>Zzqxojj3iKMfki45et4ZWqrAupQ=</wsse:Password>

<wsse:Nonce>b6QiDyhP3Ds9z24NMI0r6w==</wsse:Nonce>

<wsu:Created>2007-01-04T16:57:48.625Z</wsu:Created>

</wsse:UsernameToken>

</wsse:Security>

</soapenv:Header>

I have gone through a lot of documentation provided by SAP and SDN in an attempt to determine how and what to configure in order to generate the above SOAP header and although I am fairly sure SAP XI can perform this function I am at a loss on what needs to be done.

Their are plenty of documents describing how to do this for a Web Service generated by an SAP (WAS, R/3, XI, etc) but other than references to doing so for a third party application nothing that is concrete. Yet I am fairly certain that it is a simple process.

In one article of SAP Insider I found reference to this email address and am hoping that you will be able to assist.

Our XI is currently running WAS Netweaver 04 (640) patched at SAPKB64017.