on 04-15-2008 3:37 PM
Hi Guys,
For our B2B scenario SOAP - SOAP
we need to authenticate the users on both the sender and receiver side of the web sevice in the soap adapters
can any body suggest the best procedure to validate the customers on both the sides ?
any help would be really appreciated
Thanks,
Srini
I would suggest the use of HTTPS with SSL for validation.
You can validate the customers based on the certificate.
Cheers!!
Sidharth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sidharth,
we are planning to use certificates to validate the customer on the sender side but on the receiver side we cannot use certificates and can you plz suggest some other authentication procedures that will work with windows IIS.
we are looking for windows authentication other than NTLM ?
any suggestions would be appreciated
Thanks,
Srini
Hi Ravi,
Thanks for the quick reply and i appreciate your advice.
Send the basic authentication as part of the HTTP Header...in the tcp header...that way its not clear........ it can also be encrypted.......if thats needed
Can you explain in detail how can i acheive this and what are the steps need to be done on XI to acheive this.
Thanks,
Srini
Hi..
This is added to the tcp header..So when you recieve it in your system..you dont even see the basic authentication part..as its not part of the soap message.
Question here is..you want to add basic authentication to an outgoing is easy..tricky part is modifying the third party code to send that
inwards...
If the third party is secure enough they can send the basic authentication in the url, they are posting the msg to..that way its in the header ..and easy to implement..let me know..!!
Regards
Ravi Raman
Hi Guys,
I have solved the problem and NTLM works with PI 7.0 but we need to configure soap axis adapter
The Windows NTLM authentication is supported by Axis's CommonsHTTPSender handler and consequently it is supported by the Axis adapter's corresponding handler com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender. Read about How Can I use CommonsHTTPSender as the transport handler? if CommonsHTTPSender is not enabled on your system. Once it is enabled, you can use com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender instead of default com.sap.aii.adapter.axis.ra.transport.http.HTTPSender as the transport handler in the module configuration and set the authentication setting to NTLM and enter usename as domain\username in the channel configuration
To use CommonsHTTPHandler, the optional Jakarta-Commons-Net, Jakarta-Commons-HttpClient, Jakarta-Commons-Codec libraries are required. Make sure that these libraries are available for the Axis adapter at the deployment check page If these components are not available, you will need to include the corresponding jar files (commons-codec-1.3.jar, commons-httpclient-3.0.jar, and commons-net-1.0.0-dev.jar from the Axis 1.4 release) in aii_af_axisprovider.sda and deploy this archive (see How to prepare aii_af_axisprovider.sda?).
The provider.xml file must include the jar-name entries for these jar files, as shown in:
...
<jars>
...
<jar-name>commons-net-1.0.0-dev.jar</jar-name>
<jar-name>commons-codec-1.3.jar</jar-name>
<jar-name>commons-httpclient-3.0.jar</jar-name>
...
</jars>
Once you do all the above settings, NTLM works fine
Thanks,
Srini
Hi,
Check with this
Regards
Seshagiri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
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.