on 09-14-2009 3:31 AM
Hi ,
I have a SOAP communication channel and generated a wsdl from the sender agreement.
The WSDL requires authentication information both in design time and run time.
I would like to suppress(or default) it in both these cases. Is there any way to do this ?
Thanks for the help.
Regards
Bharath
You cannot suppress authentication for one particular interface...it will be disabled for all the scenarios involving the SOAP protocol.
However by using parameters like sap-user and sap-password in the WSDL you may avoid entering the details. Check if the way mentioned in this blog helps you: /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
From the blog:
For testing purpose it is possible to add logon data directly to the URL. The parameters are the same as in the HTTP sender
adapter: &sap-user=<username>&sap-password=<password>
Regards,
Abhishek.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Bharathwaj ,
There are two authentication mechanisams available for Web Services, one is the Basic, where we provide login details at design time and runtime in Visual Admin. There is another technique which is by enabling Client Certificates (i.e. X.508 Client certificate). You can use Client Certificate mechanisam and suppress the authorization details at design time and runtime.
Refer this blog for further information
[Consuming Web Service|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0647127850DB00972051598695383049End?blog=/pub/wlg/1012]
[Consuming Via Certificates|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a9419c0d-0301-0010-bd84-93978e7ef13a&overridelayout=true]
Regards,
Prasanna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All ,
Thanks for the responses.
When an application needs to read a WSDL to create the consumer application , we are always required to provide an user.
Can this be prevented preferrably as anonymous access or by a named user.
And at runtime ,
The client certificate idea is not simple to implement for many consumer applications and hence we are looking at some way to make it anonymous or by a named user.
Thanks
Bharathwaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.