Quantcast
Viewing all articles
Browse latest Browse all 2504

SOAP connection via http-proxy possibilities (1 Comment)

Topic by Walter Kamp

Content

We can't connect directly to the RightNow SOAP url via HTTPS. All public connections are blocked.
Instead of this we're using a (Vordel) firewall (an internal URL over HTTP and a different port number), that connects to a loadbalancer and then connects to the HTTPS-SOAP url.
So, the traphic will be via SSL from the loadbalancer, but won't be via SSL from the application to the loadbalancer.

The code in the code-block only works for https. When we use this for the internal url, the error says https was expected instead of http.
When we change this code to not use TransportWithMessageCredential, and remove the IncludeTimestamp line, the error message is: "Username token required. Cannot find in the security header".

Is there a way to connect to an internal HTTP-URL via SOAP, but solve this username token-error?

 




 

Code Block


Viewing all articles
Browse latest Browse all 2504

Trending Articles