Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Subject: RE: NTLM Cipher Error
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 8 Aug 2003 09:28:45 -0500
Message-ID: 
 <040B052AFD639D44996AF4C1FBF47818018AA2@CEPXMB03.cag.conagrafoods.net>
content-class: urn:content-classes:message
Thread-Topic: NTLM Cipher Error
Thread-Index: 
 AcNddvm4JSTKJDAyQWqgRCsheqhGDgADzF1wAAmHW6AAAF1+IAAACn/wAAB0Y1AAAb8z4AAAbQjgAAAJyuAAAFKy4AAAL7lg
From: "Rowe, David (CAG-CC MIS)" <David.Rowe2@conagrafoods.com>
To: "Commons HttpClient Project" <commons-httpclient-dev@jakarta.apache.org>

I did, and I get the error at the same ol' place.  NoClassDefFound for =
javax.crypto.CipherSpi...

Dave
PS  A little pre-thank you for all your help so far...  :)

-----Original Message-----
From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com]
Sent: Friday, August 08, 2003 9:26 AM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error


Can you comment out the check just for a heck of it?=20

Oleg

-----Original Message-----
From: Rowe, David (CAG-CC MIS) [mailto:David.Rowe2@conagrafoods.com]
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 of my program that =
simply checks for the existence of javax.crypto.CipherSpi using:

Class.forName("javax.crypto.CipherSpi");

Which shouldn't throw a ClassNotFound Exception if it exists, but if I =
remove jce.jar from the class path, it throws the exception.

Dave


-----Original Message-----
From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com]
Sent: Friday, August 08, 2003 9:19 AM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error


David,
You are not supposed to add JCE.jar to the class path. All the JCE =
classes are already available to the class loader. Just let the class =
loader do its magic.

Oleg

-----Original Message-----
From: Rowe, David (CAG-CC MIS) [mailto:David.Rowe2@conagrafoods.com]
Sent: Friday, August 08, 2003 4:13 PM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error


Okay, I freshly installed JDK 1.4.1_01 (what we're standardized with), =
added the jce.jar to the class path, I'm using Eclipse, just for =
reference.  I'm still getting the same error.  It's hitting it right =
after these debug messages

[DEBUG] HttpMethodBase - -Authorization required
[DEBUG] HttpAuthenticator - -Authenticating with the 'null' =
authentication realm at proxy.conagra.cag

So I'm assuming, it's generating the Challenge message for =
authentication at this point, which would require encryption thus, the =
JCE.

Any ideas as to why it's still not catching the crypto package?

Dave
-----Original Message-----
From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com]
Sent: Friday, August 08, 2003 8:17 AM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error


All right. I believe I know what is going on. JCE 1.2.2 is intended for =
older JDKs (1.2.x-1.3.x). As of JDK 1.4.x JCE is an integral part of the =
J2SE platform. By attempting to install JCE 1.2.2 on JDK 1.4.1 you have =
simply messed things up. Consider reinstalling Java.

Oleg

-----Original Message-----
From: Rowe, David (CAG-CC MIS) [mailto:David.Rowe2@conagrafoods.com]
Sent: Friday, August 08, 2003 3:05 PM
To: Commons HttpClient Project
Subject: RE: NTLM Cipher Error


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 <JAVA_HOME>/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)" <David.Rowe2@conagrafoods.com>
07.08.2003 21:01
Please respond to "Commons HttpClient Project"
=20
        To:     "Commons HttpClient Project"=20
<commons-httpclient-dev@jakarta.apache.org>
        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


---------------------------------------------------------------------
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


---------------------------------------------------------------------
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