WS-Security and UsernameToken 1.0 with PI 7.0

[Former Member]

Hello experts,

we use PI 7.0 and we want to establish a connection to a web service which requires the use of "Message Security 1.0 (WS-Security)" and "UsernameToken Profile 1.0". I can't find the correct settings in the SOAP adapter. Do we have to use PI 7.1 and the WS adapter to establish this connection, is it possible to install the WS adapter on PI 7.0 or is there any workaround to connect to a web service like this?

The standards are described here:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf

Best regards,

David

[stefan_grube]

This is not supported in PI 7.0 or PI 7.1

As workaround you can use the Axis adapter, but this is a little bit tricky.

Check the Axis FAQ note for the settings.

The WS-RM adapter supports this in principle, but can only be used in distinct scenarios.

Regards

Stefan

Edited by: Stefan Grube on Apr 8, 2009 6:16 PM

[Former Member]

thanks,

I think it is possible to use the plain http adapter and map the complete soap message to it.

I will try that and inform you.

Best regards,

David

[Former Member]

Hi David,

Can you Please let me know if you were able to use WS-Security and UsernameToken 1.0 with PI 7.0 or PI7.1

Thanks

Chandra

[mathias_essenpreis]

UsernameToken works with the WS-RM adapter very well, basically with every standard compliant SOAP implementation.

You have to choose User ID/password message authentication in the receiver channel, then you get a Username Token. In the receiver agreement you then enter the actual username and password to use for the call.

Choosing Asymmetric Message Signature/Encryption the messages will be signed and encrypted in a standadized WS-Security way. The signature will be performed based on a private key (stored inside a PSE of transaction STRUST of the integration server) you supply in the receiver agreement.

The other option Symmetric Message Signature/Encryption will also add signature and encryption to the SOAP message. However the signature is done with a symmetric key that is created for the particular message exchange.