DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11678>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11678

JNDIRealm times out/prompts for password with BASIC authentication





------- Additional Comments From [EMAIL PROTECTED]  2002-10-09 20:21 -------
I've noticed this bug with tomcat 4.1.12 as well. I believe this is because the 
ldap server timesout the connection after some time if there is no activity 
from the ldap client. Once the timeout occurs, if a user tries to browse a url 
that requires authentication, the bind operation in ldap fails as ldap 
connection is invalid and JNDIRealm class throws a 
javax.naming.CommunicationException. This results in authentication failure and 
user is prompted for authentication again. This is quite irritating to the 
user. When user types in uid/password second time, a new ldap connection is 
created and authentication succeeds.

I think the solution is to detect ldap connection timeout in JNDIRealm and make 
a new connection if necessary and then perform the bind for authentication. 
Hope this bug gets fixed.

-nagraj

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to