Reg OASIS WSS standards.

[Former Member]

Hi All,

We need to accept the web service requests with user name tokens. In order to achieve this, we need to make the PI webserver comply to OASIS WSS standards. How can this be done?

The example xml with the user name token is shown below. The userid and password will have to be part of the SOAP header.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rec="http://globalordering.daimler.com/services/StockApi/v1/records" xmlns:v1="http://globalordering.daimler.com/services/commonTypes/v1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

<soapenv:Header>

<wsse:Security>

<wsse:UsernameToken>

<wsse:Username>BSKAL</wsse:Username>

<wsse:Password Type="PasswordText">test0909</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

</soapenv:Header>

<soapenv:Body>

<rec:ReservationBeaprese>

<rec:MajorVersion>1</rec:MajorVersion>

<v1:CommonRequestElements>

<v1:LanguageCode>de</v1:LanguageCode>

<v1:MessageMode>parametersAndText</v1:MessageMode>

<v1:AuthorizationData>

<v1:SystemId>ALLG</v1:SystemId>

</v1:AuthorizationData>

</v1:CommonRequestElements>

<rec:Beaprerq>

<rec:OrderNr>0955900246</rec:OrderNr>

<rec:ReservingSalesUnit>559008ST</rec:ReservingSalesUnit>

</rec:Beaprerq>

</rec:ReservationBeaprese>

</soapenv:Body>

</soapenv:Envelope>

Regards,

Saipriya.

[Former Member]

Hi,

Are you using AXIS framework in SOAP Adapter for Username token security?

Regards

Anku

[Former Member]

Hi Anku,

No we are not using AXIS frame work in SOAP adapter.

Regards,

Saipriya.

[Former Member]

Ok,

can you please elaborate more on your scenario so that i can help you on this issue?

regards

Anku

[Former Member]

Hi Anku,

We have a SOAP to RFC Scenario We need to accept the web service requests with user name tokens. In order to achieve this, we need to make the PI webserver comply to OASIS WSS standards. The userid and password will have to be part of the SOAP header else the message should fail.

Regards,

Saipriya.

[Former Member]

Hi,

Could you please let me know have you already handled username token security in plain soap sender adapter or still not able to?

if yes could you please let me know what are all settings you have done.

Regards

Anku

[Former Member]

Hi Anku,

I have not got any solution yet.

Regards,

Saipriya.

[Former Member]

Hi,

I have the same requirement of using the Username security in my project so for that i have used AXIS framework in soap adpater.

regards

Anku

[Former Member]

Hi Anku,

Could you please let me know what all settings you have made to use AXIS adapter Framework?

If i use these settings will the authentication issue solve? and will i be able to see the header info in payload?

Regards,

Saipriya.

[Former Member]

Hi,

Please go through SAP Note 1039369 ( FAQ XI Axis Adapter) as it will give you complete idea about how to install AXIS framework in PI

If you face any issues in installation do let me know.

And regarding header info do you mean you want to see web security tags in PI(sxmb_moni)?Please clarify this

Regards

Anku chopra

[Former Member]

Hi Anku,

We followed Axis Adapter framework FAQ and deployed relevent jars to server and also set the module parameters of SOAP_OUT channel accordingly. But we are getting the following error while SOAP call.

?xml version="1.0" encoding="utf-8"?>

<soapenv:Envelope xmlns oapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Body>

<soapenv:Fault>

<faultcode xmlns="">soapenv erver.generalException</faultcode>

<faultstring xmlns="">WSDoAllReceiver: security processing failed; nested exception is:

org.apache.ws.security.WSSecurityException: The security token could not be authenticated or authorized</faultstring>

<detail xmlns="">

Any pointers to this will be highly appriciated.

Regards,

Saipriya.

[Former Member]

HI ,

i have installed the SDA as per the SAP notes. and the servlet output says it is deployed.

but i still cannot see the AXIS Adapter in Integration Builder (Configuration) ,

i mean i still cannot see "AXIS" as an option for message protocol in the channel and same for transport protocol.

do i need to do anything after deploying the SDA?

Thanks

Chandra