cancel
Showing results for 
Search instead for 
Did you mean: 

Sender SOAP adapter without authentication

Former Member
0 Kudos

Dear All,

I am working on one of our customer requirement where i need to send data to SAP ECC 6.0 using SOAP (Sender) and RFC (Receiver).

My scenario is SOAP (Sender) to RFC (Receiver). While configuring the SOAP sender adapter i am selecting 'HTTP' and my QOS is 'Best Effort' as it is a synchronous call.

The Web service URL looks like as follows :

http://xiserver:50000/XISOAPAdapter/MessageServlet?channel=:BS_WROUTE:SOAP_SEN_ROUTE_DATA&version=3....

The problem i am facing is while testing this web service {generated by PI 7.0 (in ID)} it is asking for user name and Password.

Can somebody suggest me while testing :

1) how can we avoid user name and Password?

2) Can we attach user name and Password in our SOAP URL? if yes so please suggest me how to attach this.

Thanks

Honey

Accepted Solutions (0)

Answers (1)

Answers (1)

AaronLong
Advisor
Advisor
0 Kudos

add &user=youruser&password=yourpassword

or have SSO configured. if you are using a browser, it should work after your first log on.

Former Member
0 Kudos

Dear Aaron,

Thanks for your response.

I have edited my wsdl with &user=youruser&password=yourpassword and also &sap-user=youruser&sap-password=yourpassword, and I am testing it through SOAP UI tool but it is still asking for username and password.

Also can you please suggest how to do this SSO configuration.

Thanks

Honey

stefan_grube
Active Contributor
0 Kudos

> add &user=youruser&password=yourpassword

This is not supported with SOAP adapter.

former_member200962
Active Contributor
0 Kudos

Hi Stefan,

The earlier version of the SOAP FAQ (https://service.sap.com/sap/support/notes/856597), if I remember properly, had a mention of the use of sap-user and sap-password in the URL(for testing purposes). Now the note seems to have been modified and the reference has been removed, may be this was the confusion. Is my understanding correct?

Thanks,

Abhishek.

Former Member
0 Kudos

Dear Stefan,

Thanks for your reply.

If I am using ABAP Port 8000 for my scenario and my URL is as follows :

http://xiserver:8000/XISOAPAdapter/MessageServlet?channel=:BS_WROUTE:SOAP_SEN_ROUTE_DATA

Can i not use this additional string &sap-user=user&sap-password to provide the user name and password in wsdl??

my new URL would be like this:

http://xiserver:8000/XISOAPAdapter/MessageServlet?channel=:BS_WROUTE:SOAP_SEN_ROUTE_DATA&sap-user=us...

Please suggest how can i avoid the credentials.

Thanks

Honey

former_member200962
Active Contributor
0 Kudos
Can i not use this additional string &sap-user=user&sap-password to provide the user name and password in wsdl??

No you cannot use this.

Check the reply from Bhavesh in this thread:

If you want to refer more similar threads check this:

https://forums.sdn.sap.com/search.jspa?threadID=&q=%22remove+authentication%22&objID=f44&dateRange=a...

Regards,

Abhishek.

stefan_grube
Active Contributor
0 Kudos

> The earlier version of the SOAP FAQ (https://service.sap.com/sap/support/notes/856597), if I remember properly, had a mention of the use of sap-user and sap-password in the URL(for testing purposes).

sap-user and sap-password works only for ABAP based adapters.

For testing you can use following work around:

https://www.sdn.sap.com/irj/scn/weblogs?blog=/cs/weblog/print/wlg/4502

Former Member
0 Kudos

Dear Abhishek,

Can you please suggest any other way to disable or avoid user name and password while web services call.

Our requirement is to invoke the PI generated web service without any authentication.

Thanks

Honey

former_member200962
Active Contributor
0 Kudos

AFAIK the procedure to remove authentication will remove it for all the SOAP scenarios and cannot be achieved for a single scenario ......the procedure is as mentioned in the thread given in the previous reply....there seems to be no other option available

Former Member
0 Kudos

Hey

If you are passing message to adapter engine of XI,then you wont be able to add user Id and password to the URL or in the webservice.we use this option if we want to monitor sender SOAP adapter,want to enable ASMA for sender SOAP or any other reason for which sender SOAP is required.

If you are passing message directly to Integration engine of XI via SOAP adapter(SOAP behaves like HTTP in this case) then you can specify the User ID and password in the URL(as we specify for HTTP).the way URL is generated in WSDL(ID->Tools->Generate webservice) will be different(will use Propose URL options instead of making URL manually)

Check for Stefan Grube's blog for this.

Thanks

Aamir

Former Member
0 Kudos

Dear Aamir,

My only ojective is to call the RFC and get the response back using SOAP adapter.

Can I try Propose URL while generate the wsdl in ID and then add &sap-username=user&sap-password=password

Please suggest.

Thanks

Honey

Former Member
0 Kudos

Hey

Yes,you can do that.

/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine

Thanks

Aamir

Former Member
0 Kudos

Hello,

I am having the same problem. I changed my URL to point to the integration server and added the username and password in the URL and I am still getting the request (pop-up) for a username and password. My URL looks like below:

http://<hostname>:8070/sap/xi/engine?type=entry&amp;version=3.0&amp;Sender.Service=<service>&amp;Int...

Can you please help me? Is there anything else I need to do?

I would really appreciate your help.

Thank you,

Rhonda

Former Member
0 Kudos

Hey

Just want to make sure,did you generate the WSDL file again and used propose URL(instead of giving your own URL).

also please try to delete/refresh cookies in the sender application and see if it helps.

The URL you have mentioned looks good to me.

Thanks

Aamir

Former Member
0 Kudos

Hello,

Yes, I did regenerate the wsdl using the "Propose URL" and then added the username and password to the end, but I am still getting the request for a username and password.

If you have any other ideas, I would really appreciate it.

Thank you,

Rhonda