stage | group | info |
---|---|---|
Manage |
Authentication and Authorization |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments |
If you use a password to sign in to GitLab, a strong password is very important. A weak or guessable password makes it easier for unauthorized people to log into your account.
Some organizations require you to meet certain requirements when choosing a password.
Improve the security of your account with two-factor authentication
You can choose a password when you create a user account.
If you register your account using an external authentication and authorization provider, you do not need to choose a password. GitLab sets a random, unique, and secure password for you.
Password reset emails sent to any verified email address introduced in GitLab 16.1.
You can change your password. GitLab enforces password requirements when you choose your new password.
- On the left sidebar, select your avatar.
- Select Edit profile.
- On the left sidebar, select Password.
- In the Current password text box, enter your current password.
- In the New password and Password confirmation text box, enter your new password.
- Select Save password.
If you do not know your current password, select I forgot my password and complete the form. A password reset email is sent to the email address you enter into this form, provided that the email address is verified. If you enter an unverified email address into this form, no email is sent, and you see the following message:
"If your email address exists in our database, you will receive a password recovery link at your email address in a few minutes."
NOTE: Your account can have more than one verified email address, and any email address associated with your account can be verified.
Your passwords must meet a set of requirements when:
- You choose a password during registration.
- You choose a new password using the forgotten password reset flow.
- You change your password proactively.
- You change your password after it expires.
- An an administrator creates your account.
- An administrator updates your account.
By default GitLab enforces the following password requirements:
- Minimum and maximum password lengths. For example, see the settings for GitLab.com.
- Disallowing weak passwords.
Self-managed installations can configure the following additional password requirements:
- Introduced in GitLab 15.4 with a flag named
block_weak_passwords
, weak passwords aren't accepted. Disabled by default on self-managed.- Enabled on GitLab.com in GitLab 15.6.
- Generally available and enabled on self-managed in GitLab 15.7. Feature flag
block_weak_passwords
removed.
GitLab disallows weak passwords. Your password is considered weak when it:
- Matches one of 4500+ known, breached passwords.
- Contains part of your name, username, or email address.
- Contains a predictable word (for example,
gitlab
ordevops
).
Weak passwords are rejected with the error message: Password must not contain commonly used combinations of words and letters.