DO NOT REPLY [Bug 18004] New: - JDBCRealm.authenticate() eats SQLExceptions and should not

[bu...@apache.org]

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=18004>.
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=18004

JDBCRealm.authenticate() eats SQLExceptions and should not

           Summary: JDBCRealm.authenticate() eats SQLExceptions and should
                    not
           Product: Tomcat 4
           Version: 4.1.18
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jswap@yahoo.com


It is extremely frustrating for the end-user when he attempts to login by using 
a CORRECT user name and password, only to be notified that the login failed, 
and with no further explanation (this occurs when an SQLException is thrown 
during the authenticate process).  The exception is being hidden from the user, 
giving the false impression that the wrong username and/or password was 
entered, when in actuality there was a database problem. 

The JDBCRealm.authenticate(String, String) method cannot declare itself to 
throw SQLExceptions since it implements the Realm interface, so I propose the 
SQLException be wrapped and re-thrown as a RuntimeException. This is not an 
elegant solution, but is vastly superior to the current behavior, which greatly 
frustrates the end-user.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org