You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is currently the case for prod (old CAS) but should be checked with CAS5.
If I change my account to have locked=true I am still able to login via both CAS and Google login. If I then change the activated to be false (while keeping locked=true), then I can't login via CAS (invalid credentials) but I can still login via Google.
Expected behaviour is to not allow people to login if either activated=false or locked=true. E.g.
Also, it would be better for the user to get a more specific error message if the account is locked and or not activated. If the user enters the correct password, then let them know the account is locked on not activated and provide email address to send support an email (populating subject line and body with important details such as userId and error message).
The text was updated successfully, but these errors were encountered:
This is currently the case for prod (old CAS) but should be checked with CAS5.
If I change my account to have
locked=true
I am still able to login via both CAS and Google login. If I then change theactivated
to befalse
(while keepinglocked=true
), then I can't login via CAS (invalid credentials) but I can still login via Google.Expected behaviour is to not allow people to login if either
activated=false
orlocked=true
. E.g.activated=true | locked=true -> block login
activated=true | locked=false -> allow login
activated=false | locked=true -> block login
activated=false | locked=false -> block login
Also, it would be better for the user to get a more specific error message if the account is locked and or not activated. If the user enters the correct password, then let them know the account is locked on not activated and provide email address to send support an email (populating subject line and body with important details such as userId and error message).
The text was updated successfully, but these errors were encountered: