Deactivated User Unable to Reactivate Account by Signing In
Original Summary
Summary:
According to GitLab's documentation, a deactivated user should be able to reactivate their account simply by signing in.
Actual Behavior:
When a user account is deactivated and then an attempt is made to sign in with that user's credentials, an error message is received stating, "Your account has been deactivated by your admin. Please log back in to reactivate your account". However, attempting to sign in again results in the same error, effectively preventing the user from reactivating their account.
Steps to Reproduce:
- Deactivate a user account from the admin interface.
- Navigate to the GitLab sign-in page.
- Try signing in with the credentials of the deactivated user.
- Observe the error message that the account has been deactivated.
- Attempt to sign in again, and notice that the same error persists.
This discrepancy between the actual behavior and what is stated in the documentation results in an inability for the user to regain access to their account unless the administrator intervenes manually.
Summary
According to GitLab's documentation, a deactivated user should be able to reactivate their account simply by signing in or having the admin re-activate their account.
The problem occurs when a deactivated user tries to re-activate their account by signing in.
Relevant Screenshots
Current Behaviour
When an admin deactivates a user account and the user tries to sign-in, an error is shown "Your account has been deactivated by your admin. Please log back in to reactivate your account"
Expected Behaviour
When an admin deactivates a user account and the user tries to sign-in, an error is shown "Your account has been deactivated by your admin. Please log back in to reactivate your account"
Steps to Reproduce
- Deactivate a user account from the admin interface
- Navigate to the GitLab sign-in page
- Try signing in with the credentials of the deactivated user
- Observe the error message that the account has been deactivated
- Attempt to sign in again, and notice that the same error persists