https://bz.apache.org/bugzilla/show_bug.cgi?id=60202
--- Comment #4 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to Remy Maucherat from comment #3) > The realm doesn't and shouldn't throw exceptions at all :) Look at the lock > out realm code. How should the Realm behave if there is a communications error? I assert that throwing an exception is a perfectly reasonable thing to do. The current Realm code is irrelevant. It will behave however we want it to behave. I'm suggesting a change to the behavior, not asking why it doesn't behave in a way that it wasn't programmed to do. It's not LockOutRealm that you need to read, it's LDAPRealm, which shows that it catches exceptions like CommunicationException (a transient, non-authentication-related problem) and returns null which makes it look the same as an authentication problem, which is isn't. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
