cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP URL requires authentication even after enclosing user and pw

sherin_jose4
Participant
0 Kudos

Hi,

Currently i have generated a SOAP url and had provided it to the source system owners. All they say is that when they enter the URL in the Internet Explorer, it asked for the username and password again even after adding it to the URL. Also when they integrated it to their application, it throwed an error "Transport error: 401 Error: Unauthorized"

The URL i shared is in the below format,

https://<HostName>:<Port>/XISOAPAdapter/MessageServlet?channel=:<BusinessSystem>:<CommunicationChannel>&nosoap=true&sap-user=<username>&sap-password=<password>

Please help me if i am missing something in this.

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member184681
Active Contributor
0 Kudos

Hi,

In fact, what Mark mentioned is true. Let me throw some more light to it. You can only include the username and password in the SOAP call to PI if you post the SOAP message directly to the Integration Engine, without using sender SOAP adapter. This approach was described by Stefan Grube in his blog here:

As a result, you would have to use a different URL to post your calls:

http://hostname:port/sap/xi/engine?type=entry&version=3.0&Sender.Service=<service>&Interface=<namespace>^<service_interface>&sap-user=<>user&sap-password=<password>

Alternatively (and this is how I would personally do it), you can include the username and password in the HTTP header attributes, as I described here:

Thanks to that, you do use the sender SOAP adapter, and achieve some more security thanks to not providing the user name and password in the URL.

Hope this helps,

Greg

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

&sap-user=<username>&sap-password=<password>

Correct me if I'm wrong but I think appending this only works when sending to the integration engine e.g via propose URL in WSDL generation.

Regards,

Mark

former_member181985
Active Contributor
0 Kudos

SOAP inbound URL supports basic authentication and hence if you provide user name & password in the URL as parameters it wont accept.

Edited by: Praveen Gujjeti on Mar 9, 2012 11:08 AM

sherin_jose4
Participant
0 Kudos

Is it like passing the username and password in the HTTP headers is the only way to connect to the XI system from another application ?

Former Member
0 Kudos

Hi,

401 means its an authentication issue so please check what ever you are giving the credentials those are correct or not (when your customer sending the data he should give those credentials).

Below links should be useful to you

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50d69314-1be0-2b10-11ab-8045021f0...

http://pcsupport.about.com/od/findbyerrormessage/a/401error.htm (OR) check SAP OSS Note 856897

Regards,

Venkata Ramesh