XI Web Service Authentication problem

[Former Member]

Hi,

I have a XI Web Service that our third-party PeopleSoft client is trying to consume. I tested the Web Service and that works. I used SOAP client testing tool that I have which posts SOAp message to the web service URL. Before i use this tool using Internext Explorer, I attempt to connect to the Web Service URL (by putting the entire web service URL in the Address Bar), it prompts me for the user name & password and upon successful authentication, MessageServlet gives me a success message.Once authenticated, i am successfully able to post SOAP messages to the Web Service URL.

I provided my PeopleSoft team with the WSDL document, they uploaded into their system, made some configs, and the SOAP message that they are generating is as below

As you can see in the SOAp message, they are attempting to pass the user name and password in SOAP header and I understand XI ignores SOAP headers OR that is at least not the way to authenticate.

Shouldn't they be able to somehow authenticate themselves against SOAP adapter using User name and password that we provided them with and the send SOAP messages?

********<soap:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Header>

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

<wsse:UsernameToken><wsse:Username>user name</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password></wsse:UsernameToken></wsse:Security></soap:Header><soap:Body><MI_EMP_ADDR_CHG_OSSERVICE xmlns="https://pics.sco.ca.gov"><PERSON_ID>BB000001</PERSON_ID><START_DATE>20100501</START_DATE><ADDR_LINE1>100 MAIN ST</ADDR_LINE1><ADDR_LINE2/><CITY>CORONA</CITY><COUNTY>RIVERSIDE</COUNTY><STATE>CA</STATE><ZIP_CODE>91881</ZIP_CODE></MI_EMP_ADDR_CHG_OSSERVICE></soap:Body></soap:Envelope>

****************

I will appreciate any ideas.

Thanks,

Saurabh

[Former Member]

Indeed, they should take care of the authentication according to supported XI mechanisms, as explained here :

http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm

There is also a note #891877 that explains security level settings for SOAP adapter

Chris