Oleg,
Again, I appreciate your ongoing help. I have made the changes
according to your recommendations in our previous email.
1. Context Logging - Done
2. I was able to GET the secure file, so I am being authenticated
correctly. I printed the file to the console.
3. Still using NTLM
- Server:
Microsoft-IIS/5.0[\r][\
n]
2004/09/30 10:05:30:417 CDT [DEBUG] header - Date: Thu, 30 Sep 2004
15:05:27
GMT[\r][\n]
2004/09/30 10:05:30:417 CDT [DEBUG] header - WWW-Authenticate:
Negotiate[\r]
[\n]
2004/09/30 10:05:30:417 CDT [DEBUG] header - WWW-Authenticate:
NTLM[\r][\n]
2004/09/30 10:05
) Consider executing GET or HEAD against a protected URL on the server
to trigger authentication prior to executing the POST with the payload
(3) If you have access to the server, consider turning off NTLM
authentication. Since you use SSL there's no point in using NTLM. Basic
authentication over SSL
All,
I need help implementing a Commons HttpClient solution to post files to
a web server via an ASP page. This seems somewhat straightforward, but
I am having trouble with the NTLM authentication.
Code Snippet:
String url =
https://keystone.ibanksystems.com/carlsontest/siteman.asp?u=Yd=c:\\im
Christopher,
What is exactly the problem?
The authentication succeeded:
HTTP/1.1 200 OK
Session cookie has been sent:
ASPSESSIONIDAQQBDABR=LMNNMHNALPPKIBENMNNANHGP
NTLM authentication scheme is a stateful one and requires multiple
challenges/responses. The first 401 Access Denied response
To: Commons HttpClient Project
Subject: Re: HttpClient + HTTPS + NTLM Authentication = HTTP/1.1
401Access Denied
Christopher,
What is exactly the problem?
The authentication succeeded:
HTTP/1.1 200 OK
Session cookie has been sent:
ASPSESSIONIDAQQBDABR=LMNNMHNALPPKIBENMNNANHGP
NTLM authentication
HttpClient Project
Subject: Re: HttpClient + HTTPS + NTLM Authentication = HTTP/1.1
401Access Denied
Christopher,
What is exactly the problem?
The authentication succeeded:
HTTP/1.1 200 OK
Session cookie has been sent:
ASPSESSIONIDAQQBDABR=LMNNMHNALPPKIBENMNNANHGP
NTLM authentication
Mike, thanks for the answer for my previous question.
I have one more clarification regarding specifying the realm when setting credentials.
Is it okay to specify null value for realm when setting credentials for NTLM
authentication. Does specifying null value, cause any security violation
Hi Karthi,
Using null for the NTLM realm is the way to go. This is covered in a
little more detail at
http://jakarta.apache.org/commons/httpclient/authentication.html.
Mike
Karthikeyani K wrote:
Mike, thanks for the answer for my previous question.
I have one more clarification regarding
Thanks a lot Mike.
Michael Becke [EMAIL PROTECTED] wrote:Hi Karthi,
Using null for the NTLM realm is the way to go. This is covered in a
little more detail at
.
Mike
Karthikeyani K wrote:
Mike, thanks for the answer for my previous question.
I have one more clarification regarding
Hi Andre-John,
I have just got my friend to try connecting to out intranet web server
with
Safari and it does not support NTLM authentication. The only two web
clients
on the platform that do suppor it are Mozilla variety and Internet
Explorer.
Though I can't confirm whether they use
PROTECTED]
cc
Subject
Re: NTLM authentication to an MS Exchange web page account using HTTP
Client V2.0
Roland Weber wrote:
If the latter is true, there still might be a platform-independent class
somewhere in sun.* or com.sun.*.
Roland, you can safely call the sun.* and com.sun.* packages
a JNI solution would lock out.
regards
Andre
-Original Message-
From: Adrian Sutton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 7:49 PM
To: Commons HttpClient Project
Subject: Re: NTLM authentication to an MS Exchange web page account
using HTTP Client V2.0
Hi Steve,
There's
-Original Message-
From: Adrian Sutton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 22, 2004 4:20 PM
To: Commons HttpClient Project
Subject: Re: NTLM authentication to an MS Exchange web page account using HTTP Client
V2.0
This sounds very much like the webserver isn't really using NTLM
but it's a fairly low priority (not a single user has complained
yet - presumably because few of our users use NTLM). If you do find
out how to do it please do let us know.
Regards,
Adrian Sutton.
On 24/06/2004, at 2:31 AM, Steve Johnson wrote:
Hi All,
Thanks again Adrian, very helpful
(authUserNameAppendDomainWithBackSlash + settings.getAuthUserName(),
settings.getAuthPassword(),
settings.getHost(), settings.getAuthDomain())
The comments on the interface say that only the username should be passed in, and NOT
the domain.
For other NTLM pages it works to use only
This sounds very much like the webserver isn't really using NTLM but is
using Digest/Basic instead. If it really were using NTLM passing in
DOMAIN\User would definitely not work because HttpClient doesn't check
for that case. That would also explain why the realm isn't what you
expect. I'd
and this
code seems to work perfectly.
Regards
Xavier Frisaye
-Original Message-
From: Fuhrmann, Hauke [mailto:[EMAIL PROTECTED]
Sent: mercredi 26 mai 2004 11:44
To: 'Commons HttpClient Project'
Subject: AW: NTLM authentication problem
Hi there,
I'm kinda frustrated here. Not your fault at all
]
Gesendet: Montag, 3. Mai 2004 16:32
An: Commons HttpClient Project
Betreff: RE: NTLM authentication problem
Hauke,
NTLM problems are notoriously difficult to troubleshoot.
Usually it all boils down to extensive guesswork.
(1) is user name in the fully-qualified format:
domain
Lili,
There's nothing in the log that could suggest a flaw in HttpClient's authentication
logic. Everything appears sane as far as the authentication is concerned. Proxy
authentication was successful. The trouble appears to be caused by the NTLM host
server which does not seem to accept
Hi Lili,
Do not give up too soon. I did test BASIC proxy (using Squid stable) +
NTLM host authentication and did work. Of course, I cannot rule out that
the problem is caused by some 'peculiarities' of Microsoft Proxy
implementation.
Please try disabling anonymous access to the host server
Hi, Oleg:
Anonymous was disabled (only NTLM is enabled).
Our customer requires Microsoft proxy server and IIS.
lili
Our proxy server is using IIS 3.0, maybe that is too old.
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 05, 2004 11:36 AM
On Wed, 2004-05-05 at 21:58, Lili Liu wrote:
Hi, Oleg:
Anonymous was disabled (only NTLM is enabled).
Our customer requires Microsoft proxy server and IIS.
I hope they know what they are doing
lili
Our proxy server is using IIS 3.0, maybe that is too old.
If upgrade is an option, give
Lili,
Truth to be told, NTLM proxy + NTLM host authentication has never been properly
tested, because none of us (HttpClient developers) has got access to a Microsoft Proxy
installation. I would not be surprised if it did not work at all with HttpClient 2.0.
I know for a fact that BASIC proxy
Lili,
Truth to be told, NTLM proxy + NTLM host authentication has never been
properly tested, because none of us (HttpClient developers) has got
access to a Microsoft Proxy installation. I would not be surprised if
it did not work at all with HttpClient 2.0. I know for a fact that
BASIC proxy
Adrian Sutton wrote:
There is absolutely no way that
HttpClient can authenticate with both an NTLM proxy and an NTLM host at
the same time. The protocol just doesn't allow for it,
It would be worth mentioning that in a sentence or two in our
authentication guide
It's already mentioned at
http://jakarta.apache.org/commons/httpclient/authentication.html :
3. NTLM authenticates a connection and not a request, so you need to
authenticate every time a new connection is made and keeping the
connection open during authentication is vital. Due
Hi there,
I hope you can help me with a little problem I got:
I have to download a file from a MS IIS webserver which uses NTLM
authentification. The only client I performed a successful download with is
MS IE. But I have to use a Java client, so I tried the jakarta commons
httpclient. I
Hauke,
NTLM problems are notoriously difficult to troubleshoot. Usually it all boils down to
extensive guesswork.
(1) is user name in the fully-qualified format: domain/account? If yes, use the
account name only
(2) do you have any 'funny' characters in the password (like German umlauts
Hi,
I am attempting to use the httpClient component to authenticate on a
proxy which uses NTLM authentication.
I have managed to use it successfully, but only when I explicitly
provide the data for the NTCredentials for the
HttpClient.getState().setProxyCredentials().
In JDK 1.4.2, if I use
the Windows API.
cheers,
Roland
Russell, Brian [EMAIL PROTECTED]
22.03.2004 12:09
Please respond to Commons HttpClient Project
To: [EMAIL PROTECTED]
cc:
Subject:NTLM credentials.
Hi,
I am attempting to use the httpClient component to authenticate
Howdy people,
I´m a newbie in Servlet programming and I need to develop a code to
run in a Ms IIS Webserver (the code needs authenticate in the IIS using the
NTLM authentication protocol).
I found a code that will authenticate me but I have not success for
this. I downloaded
(the code needs authenticate in the IIS using the
NTLM authentication protocol).
I found a code that will authenticate me but I have not success for
this. I downloaded the .JAR and DOCs from the Jakarta homepage and if you
try to compile the following example code (found in the link
http://cvs.apache.org
HttpClient Project
Assunto: Re: NTLM authenticity problem
Get HttpClient from here:
http://jakarta.apache.org/commons/httpclient/downloads.html
Make sure you put the jar file on your classpath.
Ortwin Glück
Marcelo Muzilli (IG) wrote:
Howdy people,
I´m a newbie in Servlet programming
are of an adventurous type, feel free to
give the CVS HEAD snapshot a try to see alternate authentication in action.
Oleg
-Original Message-
From: Marcelo Muzilli (IG) [mailto:[EMAIL PROTECTED]
Sent: Friday, March 12, 2004 14:34
To: 'Commons HttpClient Project'
Subject: RES: NTLM
Thank you Oleg for your quick response.
But about my code. I will have to use what class to authenticate me in the
NTLM?
TIA,
Marcelo
-Mensagem original-
De: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]
Enviada em: sexta-feira, 12 de março de 2004 10:43
Para: Commons HttpClient
HttpClient Project'
Subject: RES: NTLM authenticity problem
Thank you Oleg for your quick response.
But about my code. I will have to use what class to authenticate me in the
NTLM?
TIA,
Marcelo
-Mensagem original-
De: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]
Enviada em: sexta-feira
Para: Commons HttpClient Project
Assunto: RE: NTLM authenticity problem
Have a look at the following document. If it does not help you to get
started, get back to me
http://jakarta.apache.org/commons/httpclient/authentication.html
Oleg
-Original Message-
From: Marcelo Muzilli (IG) [mailto
Marcelo,
HttpClient provides a _reasonable_ level of abstraction of different authentication
schemes. From the user (API) standpoint the NTLM authentication is no different from
the Basic authentication (see example below):
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src
UsernamePasswordCredentials(username, password)
);
...
The IP number is my IIS Webserver.
Marcelo Muzilli
-Mensagem original-
De: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]
Enviada em: sexta-feira, 12 de março de 2004 13:17
Para: Commons HttpClient Project
Assunto: RE: NTLM authenticity problem
Almost...
client.getState().setCredentials(
null,
200.233.96.36,
new NTCredentials(username, password, host, domain)
);
NTLM authentication does not support the concept of the realm. Leave it null.
Where 'host
Thank you!!! It´s working now.
Marcelo
-Mensagem original-
De: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]
Enviada em: sexta-feira, 12 de março de 2004 13:33
Para: Commons HttpClient Project
Assunto: RE: NTLM authenticity problem
Almost...
client.getState
Hi Adrian,
thanks for the answer so far.
What I got from MS about NTLM / NTLM2 is the following (Q239869):
-- snip --
For reference, the full range of values for the LMCompatibilityLevel
value that are supported by Windows NT 4.0 and Windows 2000 include:
* Level 0 - Send LM and NTLM
It is possible to set the minimum security that is used for programs
that use the NTLM Security Support Provider (SSP) by modifying a
registry key. So anybody may set level 5 which does not accept NTLM but
NTLMv2 only. Do you refer to that by naming Windows 2003 Server?
If so that would mean
Hi all,
the web side simply claims 'Authentication using Basic, Digest and the
encrypting NTLM (NT Lan Manager) methods'.
I could not find any information related to the implemented version of
NTLM. Is it just the older one or working with NTLMv2 also?
Many thanks in advance,
Stefan Dingfelder
I just discovered a bug introduced with the recent changes in the authentication logic
for which I bear full responsibility. Basically NTLM authentication scheme fails to
properly handle authentication failures caused by invalid credentials, and a result
HttpClient enters an infinite loop
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-12-31 14:55 ---
Alfonso,
You will need to build HttpClient from the source directly, or use the latest
nightly build (although this is the 2.1 build, not 2.0, so
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-12-30 23:52 ---
Hello, this is Alfonso again. Excuse me for the delay in testing. I've
downloaded the 2.0 rc 2 (dated Oct 13) and tried my app. The library fails
/show_bug.cgi?id=24352
NTLM Proxy and basic host authorization
--- Additional Comments From [EMAIL PROTECTED] 2003-12-29 14:07 ---
ok, thanks a lot :) - especially for being so nice towards someone *this* dumb
/show_bug.cgi?id=24352
NTLM Proxy and basic host authorization
--- Additional Comments From [EMAIL PROTECTED] 2003-12-23 14:30 ---
i just feel so dumb for asking this, but ... errrm how should i use the
patches you release here ??
they just look like cvs logs, so i suppose i have
/show_bug.cgi?id=24352
NTLM Proxy and basic host authorization
--- Additional Comments From [EMAIL PROTECTED] 2003-12-10 08:42 ---
Agreed. I'll take care of these two points. If there are no other comments or
objections I would like to commit both patches tonight around 20:00 GMT and
continue
/show_bug.cgi?id=24352
NTLM Proxy and basic host authorization
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
/show_bug.cgi?id=24352
NTLM Proxy and basic host authorization
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|NLTM Proxy and basic host |NTLM Proxy and basic host
Roland Weber wrote:
Hello Eric,
it's a question of interpretation, isn't it? If we provide an option to
prefer
Basic auth over NTLM, we violate the RFC. If we provide an option to
*disable* NTLM in certain cases, HttpClient would no longer understand
it, and has to select Basic following
and NTLM Auth, it picks NTLM. By
enabling preemptive authentication, it has to choose
Basic because that's the only thing for which there
are credentials.
regards,
Roland
anon permutation [EMAIL PROTECTED]
04.12.2003 06:16
Please respond to Commons HttpClient Project
To: [EMAIL
I'm not sure that HttpClient should do anything different.
According to section 4.6 of RFC 2617, A user agent MUST choose to use
the strongest auth- scheme it understands and request credentials from
the user based upon that challenge.
Since Basic is pretty darn weak, I'd say NTLM wins out
,
but such ability appears desirable in some cases.
Oleg
-Original Message-
From: Eric Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 15:31
To: Commons HttpClient Project
Subject: Re: Make HttpClient pick Basic Auth over NTLM?
I'm not sure that HttpClient should do
Hello Eric,
it's a question of interpretation, isn't it? If we provide an option to
prefer
Basic auth over NTLM, we violate the RFC. If we provide an option to
*disable* NTLM in certain cases, HttpClient would no longer understand
it, and has to select Basic following the rules of the RFC
Hi,
I am using a proxy server that supports both NTLM and Basic Authentications.
How do I make HttpClient use Basic Auth. instead of NTLM? I am using
2.0-rc2. Following is my code
Roger,
Just to make sure that there's no misunderstanding, Odi meant to say
domain. Please make sure that you provide the correct domain host
information to the NTCredentials constructor.
Besides, 2.0rc2 was released with a pretty nasty bug that renders NTLM
authentication completely
Hi
I'm new to HttpClient and I was hoping someone could help use the NTLM authentication
correctly. I have
the neccassary permissions because I can get to the site through Internet Explorer
without any problem.
After seeing some discussion of problems with with NTLM in -rc1 I've upgraded
]
Subject: Problems with NTLM authentication
Hi
I'm new to HttpClient and I was hoping someone could help use the NTLM
authentication correctly. I have
the neccassary permissions because I can get to the site through Internet
Explorer without any problem.
After seeing some discussion of problems
to fulfill the
request. Access to the Web Proxy service is denied. )
Regards
Roger
-Original Message-
From: Khalid Ishaque [mailto:[EMAIL PROTECTED]
Sent: 21 November 2003 17:22
To: 'Commons HttpClient Project'
Subject: RE: Problems with NTLM authentication
Try this code
requires authorization to fulfill the request. Access to the Web Proxy service is denied. )
Regards
Roger
Roger,
please read about NTLM authentication again. It is not enough to specify
a user name and password. You MUST specify the realm. null is not an
option here. You should aks your network
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 11:58 ---
Created an attachment (id=8884)
Debug log of the problem with the original rc2 sources
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 12:10 ---
If I make the following change in HttpMethodBase at line 2449
instead of
|| (status == 304) ) { // NOT MODIFIED
put
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 12:13 ---
Created an attachment (id=8886)
Results after changing HttpMethodBase#2449
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|Normal |Blocker
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 13:17 ---
Alfonso,
Unfortunately I am unable to generate a proper patch at the moment (I am at the
client's site and they have CVS port blocked
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 17:48 ---
Created an attachment (id=8890)
Patch (take 1)
-
To unsubscribe, e-mail: [EMAIL
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 17:49 ---
The patch should take of the problem. Test cases included.
Oleg
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 21:17 ---
Oleg,
Wow!!!. Thanks. Applied the patch. It now works as expected without needing my
additional modifications. Should I close the bug
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 21:38 ---
Alfonso,
First of all, thanks for tracking down this bug and helping us to fix it.
I'll commit the patch shortly and close the bug report. If you
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
][\n]
[DEBUG] wire - - Connection: close[\r][\n]
[DEBUG] wire - - Proxy-Authenticate: NTLM[\r][\n]
[DEBUG] wire - - GET http://www.apache.org/ HTTP/1.1[\r][\n]
[DEBUG] wire - - User-Agent: Jakarta
Commons-HttpClient/2.1m1[\r][\n]
[DEBUG] wire - - Proxy-Authorization: NTLM
[DEBUG] wire - - Host
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
Summary: MS Proxy with NTLM authentication set up does not work
Product: Commons
Version: 2.0 Beta 2
Platform: PC
OS/Version: Other
Status: NEW
Severity
/show_bug.cgi?id=24327
MS Proxy with NTLM authentication set up does not work
--- Additional Comments From [EMAIL PROTECTED] 2003-11-02 00:36 ---
Alfonso,
Please provide wire/debug log of the session that exhibits the problem.
Oleg
, 30 Oct 2003 11:44:35 GMT[\r][\n]
[DEBUG] wire - - Connection: close[\r][\n]
[DEBUG] wire - - Proxy-Authenticate: NTLM[\r][\n]
[DEBUG] wire - - GET http://www.apache.org/ HTTP/1.1[\r][\n]
[DEBUG] wire - - User-Agent: Jakarta Commons-HttpClient/2.1m1[\r][\n]
[DEBUG] wire - - Proxy-Authorization: NTLM
Alfonso,
Nightly builds that you are using contain experimental and unstable
code. 2.1 branch is in a state of profound flux. We are still trying to
finalise the API and simply have no bandwidth to deal with the bugs in
the experimental code. Please retest your application using the latest
I posted yesterday a message with the parts of the log that begins with wire,
(is that the wire log?) saying that the output log is identical in the two
versions of the code (rc2 and nightly). Of course, the fix perhaps
is not going the be same for the two versions.
That is the correct wire
Oleg
Nightly builds that you are using contain experimental and unstable
code. 2.1 branch is in a state of profound flux. We are still trying to
finalise the API and simply have no bandwidth to deal with the bugs in
the experimental code. Please retest your application using the latest
official
the same result, reply code 407.
Tracing through the sequence of actions and activating the debugger and
examining the publicly available documentation about NTLM
challenge/response I came to the conclusion that the problem was that
HttpMethodDirector was wrongly closing the connection after
On 23/10/03 2:29 PM, Thamm, Russell [EMAIL PROTECTED]
wrote:
Hi,
I am interested in using NTLM for authentication on my Apache based webdav
server.
I am using the Slide client (based on httpclient)
I understand that HttpClient supports NTLM but requires me to supply the user
To: Commons HttpClient Project
[EMAIL PROTECTED]
cc:
Subject:NTLM Question
Hi,
I am interested in using NTLM for authentication on my Apache based webdav
server.
I am using the Slide client (based on httpclient)
I understand that HttpClient supports NTLM
Hi,
I am interested in using NTLM for authentication on my Apache based webdav server.
I am using the Slide client (based on httpclient)
I understand that HttpClient supports NTLM but requires me to supply the user
credentials.
I want to obtain the user's logon credentials from the OS
/show_bug.cgi?id=22424
NTLM class registers Sun JCE implementation by default
--- Additional Comments From [EMAIL PROTECTED] 2003-08-15 07:00 ---
Created an attachment (id=7829)
Patch take 2. This time with docs
/show_bug.cgi?id=22424
NTLM class registers Sun JCE implementation by default
--- Additional Comments From [EMAIL PROTECTED] 2003-08-15 07:02 ---
The latest patch includes the removal of the auto-JCE configuration stuff, the
docs for that and the javadoc clean up of the NTLM classes. If I
Howdy all,
In the docs for the org.apache.commons.httpclient.NTLM class is the
note:
@deprecated this class will be made package access for 2.0beta2
However the class is still public. At this stage of the release should
we just leave the class public for 2.0 and remove it in 2.1 (or 3.0?)
or
However the class is still public. At this stage of the release should
we just leave the class public for 2.0 and remove it in 2.1 (or 3.0?)
or should we make it package access as planned?
I suggest we leave it public for the 2.0 release as it has been deprecated anyway. In
CVS HEAD NTLM
I am +1 to remove the code from 2_0 branch anyway, because it is a major
obstacle for integration. We must document the issue as you suggested,
and include it in the release notes as well. Further documentation can
be done by filing a Bug in Bugzilla, this will generate enough noise on
as well if it's not
the Sun JSSE.
Rather than trying to add the JSSE provider, the HTTP
client should simply prerequisite a correctly installed
JSSE. This would also remove the side effect of changing
the JVM's security configuration by simply loading the
NTLM class.
The only negative impact I can
Yes, you are expect to pass just a plain user name. HttpClient will automatically
qualify it with the domain name when authenticating with an NTLM server.
Oleg
-Original Message-
From: Rowe, David (CAG-CC MIS) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 19:12
To: Commons
Can you comment out the check just for a heck of it?
Oleg
-Original Message-
From: Rowe, David (CAG-CC MIS) [mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 2003 4:23 PM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error
Well, on that note, I have a check at the beginning
/show_bug.cgi?id=22424
NTLM class registers Sun JCE implementation by default
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||commons-httpclient
/show_bug.cgi?id=22424
NTLM class registers Sun JCE implementation by default
--- Additional Comments From [EMAIL PROTECTED] 2003-08-14 15:09 ---
Created an attachment (id=7819)
Patch take 1.
-
To unsubscribe, e-mail: [EMAIL
/show_bug.cgi?id=22424
NTLM class registers Sun JCE implementation by default
Summary: NTLM class registers Sun JCE implementation by default
Product: Commons
Version: 1.0 Alpha
Platform: Other
OS/Version: Other
Status: NEW
Severity
David,
If it is an option, just use Java 1.4.x that comes with JCE bundled and configured
Oleg
-Original Message-
From: Roland Weber [mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 2003 8:33 AM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error
Hello Dave
PROTECTED]
Sent: Friday, August 08, 2003 2:57 PM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error
I am using JDK 1.4.1_01, I'm somewhat new to Java so configuring the Security is kind
of a hairy thing. As far as I can tell, the java.security / policy files are correct.
Dave
On Thursday, August 14, 2003, at 03:36 pm, Michael Becke wrote:
+1 for me as well.
Me too (+1, obviously non-binding). I'm about a quarter the way through
integrating rc1 into some code and the internal JCE hidden setup would
be a total spanner-in-the-works.
--
Mike
1 - 100 of 160 matches
Mail list logo
