Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Penna <mpenna@gitlab.com>2019-06-07 17:33:31 +0300
committerMike Lewis <mlewis@gitlab.com>2019-06-07 19:38:35 +0300
commitbf926010933fa2ce9d655c0a3df3f57951832975 (patch)
tree221d2cc19c67329b4c6b8c5ded33eccd14e7bdfc /doc/security/password_length_limits.md
parentfc925583dab4dcdaf750bd4aa5d79642fc5c9871 (diff)
Various edits to security documentation
Edits to conform with CE epic 1280 SSOT standards, other improvements
Diffstat (limited to 'doc/security/password_length_limits.md')
-rw-r--r--doc/security/password_length_limits.md19
1 files changed, 16 insertions, 3 deletions
diff --git a/doc/security/password_length_limits.md b/doc/security/password_length_limits.md
index 3ad78a5c835..d78293c75c6 100644
--- a/doc/security/password_length_limits.md
+++ b/doc/security/password_length_limits.md
@@ -1,15 +1,28 @@
---
type: reference, howto
---
-
# Custom password length limits
-If you want to enforce longer user passwords you can create an extra Devise initializer with the steps below.
+If you want to enforce longer user passwords you can create an extra Devise
+initializer with the steps below.
-If you do not use the `devise_password_length.rb` initializer the password length is set to a minimum of 8 characters in `config/initializers/devise.rb`.
+If you do not use the `devise_password_length.rb` initializer the password
+length is set to a minimum of 8 characters in `config/initializers/devise.rb`.
```bash
cd /home/git/gitlab
sudo -u git -H cp config/initializers/devise_password_length.rb.example config/initializers/devise_password_length.rb
sudo -u git -H editor config/initializers/devise_password_length.rb # inspect and edit the new password length limits
```
+
+<!-- ## 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.
+
+Each scenario can be a third-level heading, e.g. `### Getting error message X`.
+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. -->