Commit 13ef42fa authored by Daniel Gruesso's avatar Daniel Gruesso

Merge branch 'docs-ip-restrict' into 'master'

Update IP restriction docs for GitLab.com

See merge request gitlab-org/gitlab!57279
parents dcf41a99 824acb35
...@@ -454,24 +454,21 @@ API requests to add a new user to a project are not possible. ...@@ -454,24 +454,21 @@ API requests to add a new user to a project are not possible.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1985) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.0. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1985) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.0.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/215410) to [GitLab Premium](https://about.gitlab.com/pricing/) in 13.1. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/215410) to [GitLab Premium](https://about.gitlab.com/pricing/) in 13.1.
NOTE:
IP access restrictions are not functioning as expected on GitLab.com. If enabled,
users cannot perform Git operations through SSH, or access projects in the UI.
For more information, [see this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/271673).
To ensure only people from your organization can access particular To ensure only people from your organization can access particular
resources, you can restrict access to groups by IP address. This setting applies to all subgroups, resources, you can restrict access to groups by IP address. This group-level setting
projects, issues, and so on. applies to:
IP access restrictions can be configured at the group level only.
This restriction applies to: - The GitLab UI, including subgroups, projects, and issues.
- The GitLab UI.
- [In GitLab 12.3 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/12874), the API. - [In GitLab 12.3 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/12874), the API.
- [In GitLab 12.4 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/32113), Git actions via SSH.
Administrators and group owners are able to access the group regardless of the IP restriction. You should consider these security implications before configuring IP address restrictions:
- **SSH requests**: While you can restrict HTTP traffic on GitLab.com with IP address restrictions,
they cause SSH requests, including Git operations over SSH, to fail. For more information,
read [issue 271673](https://gitlab.com/gitlab-org/gitlab/-/issues/271673).
- **Administrators and group owners**: Users with these permission levels can always
access the group settings, regardless of IP restriction, but the can't access projects
belonging to the group when accessing from a disallowed IP address.
To restrict group access by IP address: To restrict group access by IP address:
...@@ -480,7 +477,7 @@ To restrict group access by IP address: ...@@ -480,7 +477,7 @@ To restrict group access by IP address:
1. In the **Allow access to the following IP addresses** field, enter IP address ranges in CIDR notation. 1. In the **Allow access to the following IP addresses** field, enter IP address ranges in CIDR notation.
1. Select **Save changes**. 1. Select **Save changes**.
![Domain restriction by IP address](img/restrict-by-ip.gif) ![Domain restriction by IP address](img/restrict-by-ip.gif)
## Restrict group access by domain **(PREMIUM)** ## Restrict group access by domain **(PREMIUM)**
......
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