terça-feira, 25 de novembro de 2008 00:45Previously in the private Beta I was able to authenticate using the WebRequest.DefaultWebProxy like so....
WebProxy proxy = new WebProxy(@"http://<myProxyAddress>:8080");
proxy.Credentials =new NetworkCredential(login.UserName,login.Password,login.Domain); WebRequest.DefaultWebProxy = proxy;
Anil suggested (in another thread) that I should specify the proxy address as https:// but this resulted in another error message "The ServicePointManager does not support proxies with the https scheme"
Any idea's on how to authenticate via my Proxy?
Todas as Respostas
terça-feira, 25 de novembro de 2008 03:08Tjarvis
I shall have our folks look into it. Will get back to you soon.
terça-feira, 25 de novembro de 2008 03:58Thanks Anil, much appreciated.
terça-feira, 25 de novembro de 2008 06:10TJarvis
Here is what i have so far... Could you try this pls...
"Could it be possible that the proxy server that he is using does not support https?
I think he should be able to establish a http connection to the proxy server, which should tunnel https traffic through to SDS. This of course assumes that he trusts the proxy server. The URL in the webrequest would be https and the webproxy url would use http. It isn't necessary to use https to communicate to the proxy server.
I would also suggest contacting your system adminsitrator"
- Editado AnilredMicrosoft Employee terça-feira, 25 de novembro de 2008 19:47 Rename
terça-feira, 25 de novembro de 2008 18:53Err... for clarity - "Sitka" used to be the code name for SQL Data Services. You will notice some traces of this in the code and wire payload still today.
Ryan Dunn -- Co-Author, The .NET Developer's Guide to Directory Services Programming -- SQL Services Evangelist
terça-feira, 25 de novembro de 2008 20:38Ok, I am confused by this answer, this is what I am currently doing. i.e. the soap calls are via https and the proxy server url is specified as http. When I specified the proxy url as https the other error occurred (ServicePointManager....)
Note this proxy authentication was working fine during the private beta, its only now broken using the new service.
I am happy to speak to my admin guys, but I need to be able to verballise to them what my problem actually is, just saying; "it was working, but now it isn't" is almost certainly going to elicit the response: the problem must be with your service.
Just to restate my problem, and I am sure this is probably going to be a common scenario, surely proxies are very common.
* I work for a company that tunnels all web traffic throught a proxy server
* I need to authenticate (to the proxy server) all web requests
* rest is ok, as it simply uses my browser settings
* soap calls need to be authenticated
* previously setting the C# WebRequest object's default proxy in code worked, now it doesn't
This currently is a show stopper for me.
terça-feira, 25 de novembro de 2008 20:55
The login/password you use for the Proxy should technically be different to the login/password of your authority in ssds, unless you've somehow made them the same.
From your logic it sounds like you would be doing the following
1. Create a webproxy connection to your proxy using https://proxy, login1/password1
2. Create a httpwebrequest to ssds https://[uri_to_your_container] , login2/password2
So the question I have for you is are you using the correct proxy login/password that was given to you by your proxy admin / network admin ?? This is normally your active directories login/password...
Incidently only in the last week has my implementation of SOAP for my application started failing. I actually switched to REST just so that my app would work. I never really investigated what the issue was BUT i may now go back to trying SOAP to see if my issues are related to yours.
Make the web a beautiful place
terça-feira, 25 de novembro de 2008 21:16
Hi Liquid boy,
Thanks for your response, seems I did indeed need the "are you sure its plugged in" response. I am pulling my domain credentials from a config file (I was demo'ing this stuff a few weeks ago, and didn't want everyone to see my domain login details ;-) and of course my password changed last week, I forgot to alter my config file....DOH !
About to retry now, but that will be the problem i am sure. Thanks to all, the support in here is 1st rate.
terça-feira, 25 de novembro de 2008 21:22Just a short note to confirm that (embarassingly) it was simply a wrong password problem in my apps config file.
In case anyone else is wondering how to authenticate your web requests to your proxy server for use with the SDS soap service, the approach that works for me in C# is to create a WebProxy object and set its creditentials (usually your domain login and password), then replace the DefaultWebProxy on the WebRequest object with the new WebProxy object and voila.
- Marcado como Resposta AnilredMicrosoft Employee terça-feira, 25 de novembro de 2008 23:02