HTTPS config in SOAP receiver adapter ?

[Former Member]

Hi Guys,

I have configured the soap receiver adapter with the URL

*https://xxxx.abcd.com/xyzv/bbbb.asmx with the user authentication *

I have tested the url and the user and pw in the browser and they are working fine but the messages are failing the soap receiver adapter with the 401 unautorized error as the message from the Audit log in the RWB.

Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized. Setting message to status failed.

Do i need to configure the Java Stack for HTTPS ? The communicaion is between the XI system and a third part system internally.

any help would be appreciated ?

Thanks,

Srini

[Former Member · Accepted solution]

Srini:

I think the Username and password you tried have no authorizations to access the webservice. Could you please try to check their authentication through any other means or use some admin user name and password

[Former Member]

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

[r_s_kulkarni11]

Hi Srinivas,

I have configured the NTLM authorization using the Reciever Axis adapter....but I am still facing the 401: Authorization issue.

Can you please let me know on this?

Regards,

Rahul Kulkarni

[Former Member]

Hi Rahul

Did you solved this?

I'm struggling with this issue currently..

Thanks

Henrik

[r_s_kulkarni11]

Hi Henrik,

Are you connecting to Microsoft share point?

Can you please also try using Axis adapter?

[Former Member]

Hi Rahul

I have tried using the Axis adapter, but even that didn't Work.

It is a Microsoft platform that I need to connect to, and we got it to Work once all user auth was disabled by Microsoft side....

but still the question remains - is it possible to use NTLM auth in PI?

It should be, but is it working?

[stefan_grube]

Check this:

http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm

If this is internal, maybe you have an HTTP address as well?

Regards

Stefan

[henrique_pinto]

If you have SAP Java Cryptographic Toolkit installed and the server's certificate chain in your TrustedCAs view, it's probably just a typo in the user or password in the communication channel.

Regards,

Henrique.

[Former Member]

Hi Stefan,

I have discussed with admin guys and they say they have IIS before hitting the actual webservice and it validates the user id and pw.

It works in the browser with the HTTPS url because the pop comes asking for the id and pw but it is not the case with the xi as we enter in the soap receiver adapter configuration.

The webservice team said they dont validate the user or certificate and i dont know what exactly the IIS is doing.

This is working fine with the SOAP UI test tool.

we have discussions on Monday and mean time i want to have the suggestions from the sdn experts.

any ideas would be apprecited and awarded naturally the points

Thanks,

[stefan_grube]

> It works in the browser with the HTTPS url because the pop comes asking for the id and pw but it is not the case with the xi as we enter in the soap receiver adapter configuration.

The browser cares about the exchange of certificates automatically, but in PI you have to do this manually.

Regards

Stefan

[Former Member]

Hi Stefan,

Do i need to configure Java part for SSL and then try with the user id and pw.

If i want to go with the user id and pw authenticaton type in the soap receiver adapter, is it mandatory that i need to configure r Java for SSL or

we configure Java SSL only when certificate Authentication is required.

Can you plz clarify me with the above query

any help would be appreciated

Thanks,

Srini

[Former Member]

Hi Stefan,

I have traced the message between xi and the 3rd party server and i see the following message

java.net.ConnectException: Connection timed out: connect

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(Unknown Source)

at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.<init>(Unknown Source)

at java.net.Socket.<init>(Unknown Source)

at com.sap.aii.axis.utils.TCPGateway$Connection.run(TCPGateway.java:878)

any help would be appreciated

Thanks,

Srini

[Former Member]

Srinivas,

I configured Java for HTTPS also. I do not get the errors you mentioned.

-RK

[Former Member]

Hi RK,

I have not yet configured Java for SSL. I want to know whether we need to configure Java for SSL for user authentication.

any help would be appreciated

Thanks,

Srini

[stefan_grube]

It depends of your web service proider, what you have to configure.

So ask your system administrators to provide this information to you.

Your URL starts with HTTPS, that is a hint, that you need SSL.

When you receive a pop up in the browser, that is a hint that you need authentication additionaly.

Regards

Stefan

[Former Member]

Hi Stefan,

I have configured Java for ssl and the url https://xyz:50101/ working fine but i am still getting the 401 authentication errors in the soap receiver adapter when i check user authentication with the user id and pw.

I have asked administrators and they say like testing with the SOAP UI works fine with the credentials but i found that sap xi soap adapter dosent support the windows NTLM authentication and i need to go for soap Axis adapter to support NTLM.

Is NTLM supported in PI 7.1 with out the usage of Axis adapter or in PI 7.1 also we need to wrtire handlers ?

Thanks,

Srini

[stefan_grube]

No, NTLM is not supported with PI 7.1.

Regards

Stefan

[Former Member]

Please check with the third party system for the necessary authorization .As far as I can see you were able to connect to the system so the https communication is working.

Regards

Ratan

[agasthuri_doss]

Srini,

As Guru mentioned the User ID has NO authorization.

Regards

Agasthuri Doss