debian-mirror-gitlab/doc/user/admin_area/settings/sign_up_restrictions.md

58 lines
2.2 KiB
Markdown
Raw Normal View History

2019-09-04 21:01:54 +05:30
---
type: reference
---
2016-08-24 12:49:21 +05:30
# Sign-up restrictions
2017-08-17 22:00:37 +05:30
You can block email addresses of specific domains, or whitelist only some
2018-10-15 14:42:47 +05:30
specific domains via the **Application Settings** in the Admin area.
2017-08-17 22:00:37 +05:30
>**Note**: These restrictions are only applied during sign-up. An admin is
2019-02-15 15:39:39 +05:30
able to add a user through the admin panel with a disallowed domain. Also
2017-08-17 22:00:37 +05:30
note that the users can change their email addresses after signup to
disallowed domains.
## Whitelist email domains
> [Introduced][ce-598] in GitLab 7.11.0
You can restrict users to only signup using email addresses matching the given
domains list.
2016-08-24 12:49:21 +05:30
## Blacklist email domains
> [Introduced][ce-5259] in GitLab 8.10.
With this feature enabled, you can block email addresses of a specific domain
from creating an account on your GitLab server. This is particularly useful to
prevent spam. Disposable email addresses are usually used by malicious users to
create dummy accounts and spam issues.
2017-08-17 22:00:37 +05:30
## Settings
2016-08-24 12:49:21 +05:30
This feature can be activated via the **Application Settings** in the Admin area,
and you have the option of entering the list manually, or uploading a file with
the list.
2017-08-17 22:00:37 +05:30
Both whitelist and blacklist accept wildcards, so for example, you can use
`*.company.com` to accept every `company.com` subdomain, or `*.io` to block all
domains ending in `.io`. Domains should be separated by a whitespace,
semicolon, comma, or a new line.
2016-08-24 12:49:21 +05:30
![Domain Blacklist](img/domain_blacklist.png)
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.
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. -->
2016-08-24 12:49:21 +05:30
[ce-5259]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5259
2018-11-08 19:23:39 +05:30
[ce-598]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/598