Commit 2a577caa authored by Harsh Chouraria's avatar Harsh Chouraria Committed by Evan Read

Clarify API coverage of IP restriction

parent 980423ff
...@@ -561,8 +561,9 @@ You should consider these security implications before configuring IP address re ...@@ -561,8 +561,9 @@ You should consider these security implications before configuring IP address re
- **Administrators and group owners**: Users with these permission levels can always - **Administrators and group owners**: Users with these permission levels can always
access the group settings, regardless of IP restriction, but they cannot access projects access the group settings, regardless of IP restriction, but they cannot access projects
belonging to the group when accessing from a disallowed IP address. belonging to the group when accessing from a disallowed IP address.
- **GitLab API and runner activities**: Only the [Groups](../../api/groups.md) - **GitLab API and runner activities**: Only the [group](../../api/groups.md) (including all
and [Projects](../../api/projects.md) APIs are protected by IP address restrictions. [group resources](../../api/api_resources.md#group-resources)) APIs and [project](../../api/api_resources.md#project-resources)
(including all [project resources](../../api/api_resources.md#project-resources)) APIs are protected by IP address restrictions.
When you register a runner, it is not bound by the IP restrictions. When the runner When you register a runner, it is not bound by the IP restrictions. When the runner
requests a new job or an update to a job's state, it is also not bound by requests a new job or an update to a job's state, it is also not bound by
the IP restrictions. But when the running CI/CD job sends Git requests from a the IP restrictions. But when the running CI/CD job sends Git requests from a
......
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