Type |
Bug
|
Priority |
Critical
|
Assignee | |
RedmineID |
1098
|
Version |
tigase-server-5.2.0
|
Issue Votes (0)
Watchers (0)
Type |
Bug
|
Priority |
Critical
|
Assignee | |
RedmineID |
1098
|
Version |
tigase-server-5.2.0
|
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:
Run the Tigase server with MySQL database
Try to login with a client
Disconnect the client
Stop the database
Try to login with the client
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.