cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

pi 7.0, Soap receiver, https and proxy configuration...

0 Likes
1,819

Hi experts...

I have got a big problem with a RFC->Soap escenario. Maybe someone can help me...

I am trying to call a web service (https), without any authetication (no user-password and no client certificate) from a pi 7.0, through a proxy.

I have uploaded all the certificate tree of the service to the key store in the netweaver visual admin, and I am pretty sure that the java criptographic library has been deployed.

Calling the web service directly from my computer using SOAP-UI, works fine with the proxy settings...And with a browser from the pi server I am able to access the host of the service.

I have made some "Test cases" to see if I catch is he problem:

-Soap Receiver channel with the correct web service URL (https), and the proxy settings that works on the soap-ui:

It should works but it returns the "Connection closed from remote host"exception.

-Soap Receiver channel with the correct web service URL(https), but without any proxy settings:

I was expecting a "proxy authentication required" but I get the "Connection closed from remote host" exception.

-Soap Receiver channel with a wrong web service url (http), and with the correct proxy settings:

I was expecting a "not found" error, and i get a "Proxy authentication error".

-Soap Receiver channel with a wrong web service url (http), and without any proxy settings:

I get a "proxy authentication error", as expected...

¿Anyone knows which could be the problem?

Thanks in advance for your help.

View Entire Topic
0 Likes

Well,

It seems that the proxy uses NTLM authetication.... And the pi is not compatible with this kind of authentication...

I can not use AXIS, it is usefull to connect to NTLM authenticated web services, but the documentation says nothing about proxies....