Use of other proxy authentification schemesas UsernameOpasswordCredentials

[GoogleCodeExporter]

What steps will reproduce the problem?
1. In the course of an ESME deployment compny-internal I came across the
problem that the proxy between me and the internet needs
ntlm-authentification (username/password is not accepted)
2. So I am about to create a patch to the ProxyConfigurationClass and the
HTTPClientFactory, which allows to use e.g. the NTCredentials class 

What is the expected output? What do you see instead?
Expected is that I can cross the proxy using NTLM credentials

What version of the product are you using? On what operating system?
- just checked out from SVN

Please provide any additional information below.
- As I wrote, I am about to create patch to solve this. Please give me
feedback if the project is interested in taking over this change.

Original issue reported on code.google.com by dakoller on 17 Nov 2008 at 2:32

[GoogleCodeExporter]

I read the HttpClient 4.0 doc: 
http://hc.apache.org/httpcomponents-client/ntlm.html
"Currently HttpClient 4.0 does not provide support for the NTLM authentication 
scheme
out of the box and probably never will. The reasons for that are legal rather 
than
technical".

So I think when you're adding some other dependencies, please pay attention to 
their
licenses.

Original comment by zhoushu...@gmail.com on 17 Nov 2008 at 3:13

[GoogleCodeExporter]

I agree with Sutra. Openid4java is distributed under the Apache 2.0 license.

If a patch can be developed in a pluggable form, we can link to it and document 
it in a 
wiki page, but I don't see how we could distribute it.

Closing the issue for now.

Thank you for the offer to contribute!

Original comment by Johnny.B...@gmail.com on 1 Jan 2009 at 8:41

• Changed state: WontFix