Andrzej Wójcik (Tigase) opened 1 year ago
|
|||||||
Andrzej Wójcik (Tigase) changed state to 'In Progress' 1 year ago
|
|||||||
After short discussion with @bmalkow we decided that we can make this change without any impact on the account security. |
|||||||
Referenced from commit 1 year ago
|
|||||||
Andrzej Wójcik (Tigase) changed state to 'In QA' 1 year ago
|
|||||||
wojciech.kapcia@tigase.net batch edited 7 months ago
|
|||||||
wojciech.kapcia@tigase.net batch edited 7 months ago
|
|||||||
Andrzej Wójcik (Tigase) changed state to 'Closed' 7 months ago
|
|||||||
Referenced from commit 1 month ago
|
|||||||
Referenced from commit 1 month ago
|
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
tigase-server-8.4.0
|
Server Version |
8.4.0
|
Target Release |
1.0
|
Sprints |
n/a
|
Customer |
n/a
|
Iterations
-
tigase-server-8.4.0 Closed
Issue Votes (0)
It was brought to my attention that if account is waiting for confirmation (and due to that authentication is failing), currently Tigase reports back
temporary-auth-failure
error. This error suggest that without any user interaction, account may become accessible as the "issue" is only temporary.For blocked accounts, Tigase returns
account-disabled
error that notifies user that account is blocked and it needs to take action to actually "fix" account state.Due to the nature of the error (account pending confirmation), we should be returning
account-disabled
to let user know that some action has to be taken to enable his account.