[jcifs] Problem with JCIFS NTLM Authentication for HTTP Connections

Michael B Allen mba2000 at ioplex.com
Fri Jan 14 17:50:53 GMT 2005

On Fri, 14 Jan 2005 13:47:48 +0100
"Doan, Thi-My-Chi" <thi-my-chi.doan at hp.com> wrote:

> > Mmm, it looks like NtlmHttpURLConnection expects request properties 
> > to be 'List's. Are you certain that is the correct way to set the 
> > cookie? Are request properties not supposed to be List objects?
> Thanks for the hint! I put the cookie's values into a list and it works
> fine now.
> > Huh? So you're using NtlmHttpURLConnection with the NtlmHttpFilter? 
> > You do realize that the two features are separate? The NtlmHttpFilter
> is 
> > for authenticating clients whereas the NtlmHttpURLConnection is the
> http client.
> It's a web application, which can be accessed from :
> 1) a web browser: user is automatically authenticated using NTLM
> authentication
> 2) from a standalone Java application via servlet. User must enter their
> NT 
> username and password, which will be sent to the web application.

If it's a "standalone Java application" why not just use SmbSession.logon


Greedo shoots first? Not in my Star Wars.

More information about the jcifs mailing list