Projects tigase _server server-core Issues #196
SASL authentication does not leave trace of DB exception (#196)
Artur Hefczyc opened 1 decade ago

If there is a problem with authentication database, the user cannot login, and receives a message that authentication failed. This is fine. However, there is no trace in the log file about database problems, which makes it very hard for the admin to track the problem down.

Steps to replicate:

  1. Run the Tigase server with MySQL database

  2. Try to login with a client

  3. Disconnect the client

  4. Stop the database

  5. Try to login with the client

  6. The client cannot login but there is not details on the log file about DB being down or any problem with DB

I believe this is due to AuthRepoPlainCallbackHandler class catching the DB exception and not signaling it in any way, just setting auth to failed.

issue 1 of 1
Type
Bug
Priority
Critical
Assignee
RedmineID
1098
Version
tigase-server-5.2.0
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#196
Please wait...
Page is in error, reload to recover