Commit a62060b1 authored by Karen Carias's avatar Karen Carias

Added " How to maintain tight control over the number of active users on your...

Added " How to maintain tight control over the number of active users on your GitLab installation" to documentation
parent c30079f3
...@@ -47,3 +47,38 @@ sudo gitlab-rake gitlab:import:all_users_to_all_groups ...@@ -47,3 +47,38 @@ sudo gitlab-rake gitlab:import:all_users_to_all_groups
# installation from source # installation from source
bundle exec rake gitlab:import:all_users_to_all_groups RAILS_ENV=production bundle exec rake gitlab:import:all_users_to_all_groups RAILS_ENV=production
``` ```
## Maintain tight control over the number of active users on your GitLab installation
- Enable this setting to keep new users blocked until they have been cleared by the admin
```bash
(default: false).
block_auto_created_users: false
Base where we can search for users
Ex. ou=People,dc=gitlab,dc=example
base: ''
Filter LDAP users
Format: RFC 4515 http://tools.ietf.org/search/rfc4515
Ex. (employeeType=developer)
Note: GitLab does not support omniauth-ldap's custom filter syntax.
user_filter: ''
```
- GitLab EE only: add more LDAP servers
```bash
Choose an ID made of a-z and 0-9 . This ID will be stored in the database
so that GitLab can remember which LDAP server a user belongs to.
uswest2:
label:
host:
....
```
\ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment