Return-Path: Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 3160 invoked from network); 8 Aug 2003 13:05:33 -0000 Received: from fcrpne502d.crfc.com (204.76.113.34) by daedalus.apache.org with SMTP; 8 Aug 2003 13:05:33 -0000 Received: from CEPSMTP02.cag.conagrafoods.net (cepsmtp02.conagra.cag [172.24.58.35]) by fcrpne502d.crfc.com with SMTP id h78D5WvG021734 for ; Fri, 8 Aug 2003 08:05:32 -0500 (CDT) Received: from CEPXMB03.cag.conagrafoods.net ([172.24.62.16]) by CEPXBH02.cag.conagrafoods.net with Microsoft SMTPSVC(5.0.2195.5329); Fri, 8 Aug 2003 08:05:30 -0500 Subject: RE: NTLM Cipher Error Date: Fri, 8 Aug 2003 08:05:29 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <040B052AFD639D44996AF4C1FBF47818018A9A@CEPXMB03.cag.conagrafoods.net> content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NTLM Cipher Error Thread-Index: AcNddvm4JSTKJDAyQWqgRCsheqhGDgADzF1wAAmHW6AAAF1+IAAACn/w From: "Rowe, David (CAG-CC MIS)" To: "Commons HttpClient Project" X-OriginalArrivalTime: 08 Aug 2003 13:05:30.0775 (UTC) FILETIME=[BEC40A70:01C35DAD] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Yep, they're under that directory. jce.jar, jce1_2_2.jar, = sunjce_provider.jar, local_policy.jar, US_policy.jar. Dave -----Original Message----- From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com] Sent: Friday, August 08, 2003 8:03 AM To: Commons HttpClient Project Subject: RE: NTLM Cipher Error David, If this is indeed the case, there must be something wrong about your JDK = installation. JCE is supposed to work out of the box with Java 1.4.x. = Did you by any chance copy JCE jar files to /jre/lib/ext? Oleg -----Original Message----- From: Rowe, David (CAG-CC MIS) [mailto:David.Rowe2@conagrafoods.com] 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 -----Original Message----- From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com] Sent: Friday, August 08, 2003 3:17 AM To: Commons HttpClient Project Subject: RE: NTLM Cipher Error 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:ROLWEBER@de.ibm.com] Sent: Friday, August 08, 2003 8:33 AM To: Commons HttpClient Project Subject: RE: NTLM Cipher Error Hello Dave, NoClassDefFound errors are often misleading. If the class itself is = found,=20 but one it depends upon is not, you still get the error for the class that is=20 available and have to figure out which one is actually missing. I'm sorry I can't give you any more specific hints on this. Maybe you = can=20 use a test program that accesses the JCE directly to make sure it is = configured=20 as it should be. regards, Roland "Rowe, David (CAG-CC MIS)" 07.08.2003 21:01 Please respond to "Commons HttpClient Project" =20 To: "Commons HttpClient Project"=20 cc:=20 Subject: RE: NTLM Cipher Error As far as I can tell, everything seems to be in order. Are there any=20 special caveats regarding using the JCE (jce1_2_2.jar or jce.jar)? It=20 seems odd to have the JCE in the classpath, yet, it throws a=20 NoClassDefFound exception. Has anyone else experienced this? Dave -----Original Message----- From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com] Sent: Thursday, August 07, 2003 11:03 AM To: Commons HttpClient Project Subject: RE: NTLM Cipher Error >=20 > Is there anything blatantly obvious here? All I need to do is be able = to access internet resources, through a Proxy (ISA) > that uses NTLM=20 Authentication. David, I'll make sure that HttpClient picks up the correct credentials=20 when authenticating with a proxy. As far as JCE is concerned, this is a=20 standard Java extension that HttpClient relies upon, but has no direct=20 control of. You have to ensure that JCE is properly configured in order = to=20 get NTLM authentication support in HttpClient to work. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail:=20 commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail:=20 commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail:=20 commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail:=20 commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: = commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: = commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: = commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: = commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: = commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: = commons-httpclient-dev-help@jakarta.apache.org