[jcifs] strange behavior
Michael B Allen
mba2000 at ioplex.com
Fri Jul 8 21:48:53 GMT 2005
On Fri, 8 Jul 2005 14:49:17 -0400
"Aaron J Weber" <aweber at comcast.net> wrote:
> Thanks for all those tips. I tested Logon.class against the .115 DC, and it succeeded every time! How could that be? Is that code significantly different? Is it possible that 115 has its IPC$ service closed somehow, someway?
> Also, I noticed with my app that there are a LOT of authentication requests...for example when my main page comes-up (which uses frames), there are at least 4 auth requests for the user...and as the user progresses thru the app, it continues. That's gonna irk the networking guys a bit. I looked thru the different config settings, but didn't find anything to "cache" the users credentials and/or allow the user to remain "auto-authenticated" for a period of time.
That's bad. Once a user has authenticated the NtlmPasswordAuthentication
object is stored in the HttpSession. Perhaps there is something odd
about your container.
More information about the jcifs