2019-09-04 21:01:54 +05:30
---
2021-02-22 17:27:13 +05:30
stage: Manage
2022-04-04 11:22:00 +05:30
group: Authentication and Authorization
2022-11-25 23:54:43 +05:30
info: 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
2019-09-04 21:01:54 +05:30
type: reference, howto
---
2019-09-30 21:07:59 +05:30
2021-09-04 01:27:46 +05:30
# Custom password length limits **(FREE SELF)**
2014-09-02 18:07:02 +05:30
2021-09-04 01:27:46 +05:30
By default, GitLab supports passwords with the following lengths:
2020-01-01 13:55:28 +05:30
2021-09-04 01:27:46 +05:30
- Minimum: 8 characters
- Maximum: 128 characters
2020-01-01 13:55:28 +05:30
2023-01-13 00:05:48 +05:30
You can only change the minimum password length. Changing the minimum length does not affect existing user passwords.
Existing users are not asked to reset their password to adhere to the new limits. The new limit restriction applies only
during new user sign-ups and when an existing user performs a password reset.
2020-01-01 13:55:28 +05:30
2023-01-13 00:05:48 +05:30
## Modify minimum password length
2021-01-29 00:20:46 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/20661) in GitLab 12.6
The user password length is set to a minimum of 8 characters by default.
To change the minimum password length using GitLab UI:
2022-10-11 01:57:18 +05:30
1. On the top bar, select **Main menu > Admin** .
2021-09-04 01:27:46 +05:30
1. On the left sidebar, select **Settings > General** and expand **Sign-up restrictions** .
1. Enter a **Minimum password length** value greater than or equal to `8` .
1. Select **Save changes** .
2020-01-01 13:55:28 +05:30
2019-09-04 21:01:54 +05:30
<!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
one might have when setting this up, or when something is changed, or on upgrading, it's
important to describe those, too. Think of things that may go wrong and include them here.
This is important to minimize requests for support, and to avoid doc comments with
questions that you know someone might ask.
2023-01-13 00:05:48 +05:30
Each scenario can be a third-level heading, for example `### Getting error message X` .
2019-09-04 21:01:54 +05:30
If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. -->
