cancel
Showing results for 
Search instead for 
Did you mean: 

Adding WS Security in SOAP header for calling soap services from PI

subhro_de
Active Participant
0 Kudos

When i am calling a wss enabled webservice from soapui with the header parameters

Username , Password and Password Type - PasswordText , it is able to get results. The soapui tool automatically adds the following in the soap header -

<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

<wsse:UsernameToken wsu:Id="UsernameToken-9368150" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

<wsse:Username>xxxxx</wsse:Username>

<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">xxxxx</wsse:Password>

<wsse:Nonce>aOA1P6t2hJPRyuraQ/IliQ==</wsse:Nonce>

<wsu:Created>2009-07-10T14:58:33.781Z</wsu:Created>

</wsse:UsernameToken>

</wsse:Security>

However , in PI when the following configurations are made -

Web Services Security option selected in soap receiver adapter

In Receiver Agrrement -

Security Standard - http://docs.oasis ....

Security Procedure (Request) - None

Security Procedure (response) - None

the user tokens don't seem to generated and it is giving an authentication error . Is there any process of generating this in the outgoing soap header from PI.

SOAP Axis framework is not installed at present and working on PI 7.1 SP6.

Looking forward for your replies

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

same issue for me too.

Try using WS adapter on receiver side .

If you are able to attach SOAP header with WSSE fields using SOAP adapter at reciever channel let me know how you did it.