[jcifs] NtlmHttpFilter caching question

AJ Weber aweber at comcast.net
Sun Nov 16 22:10:27 GMT 2008


I'm trying to fit the filter atop a J2EE framework.  For whatever reason, the filter ends-up having to re-authenticate really frequently.

I have tried a bunch of ideas around caching (with ehcache) and with setting a cookie as a flag that the filter does not need to attempt re-auth, I (want to) "accept" the browser's credentials as they are.

The problem is that it somehow ends-up putting the webapp in a loop if I simply return the existing ntlm object from the session (like, if I check for it early in the negotiate and if it exists and is not null, I simply tell negotiate to return that ntlm object.  I would expect the filter-chain to just take it from there.  The ntlm object DOES exist in the session, but apparently the "Authorization" header gets re-set and even if I detect in there that the ntlm object already exists, returning it causes this issue.  If I let the authentication run its course, it works fine, but I'm going to get in a lot of trouble with the network admins and AD guys for all the unnecessary traffic.

Something's wildly amiss.

Any ideas?

-------------- next part --------------
HTML attachment scrubbed and removed

More information about the jcifs mailing list