diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-06-27 03:08:19 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-06-27 03:08:19 +0300 |
| commit | c937ca4f20d47f5cc87300eae29dbb98ad0a956c (patch) | |
| tree | 761a8febb2e27f7ac1a04c8f077546125818e546 /doc/user | |
| parent | 972f10aa90a29b400ee84ee66e720ec633102b33 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
| -rw-r--r-- | doc/user/clusters/agent/ci_cd_workflow.md | 4 | ||||
| -rw-r--r-- | doc/user/group/index.md | 5 | ||||
| -rw-r--r-- | doc/user/ssh.md | 2 |
3 files changed, 7 insertions, 4 deletions
diff --git a/doc/user/clusters/agent/ci_cd_workflow.md b/doc/user/clusters/agent/ci_cd_workflow.md index 9ed69f80024..01ec13c02ef 100644 --- a/doc/user/clusters/agent/ci_cd_workflow.md +++ b/doc/user/clusters/agent/ci_cd_workflow.md @@ -54,6 +54,8 @@ You can authorize the agent to access individual projects, or authorize a group so all projects within have access. For added security, you can also [use impersonation](#use-impersonation-to-restrict-project-and-group-access). +Authorization configuration can take one or two minutes to propagate. + ### Authorize the agent to access your projects > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/327850) in GitLab 14.4. @@ -170,6 +172,8 @@ You can impersonate: - The CI/CD job that accesses the cluster. - A specific user or system account defined within the cluster. +Authorization configuration can take one or two minutes to propagate. + ### Impersonate the agent The agent is impersonated by default. You don't need to do anything to impersonate it. diff --git a/doc/user/group/index.md b/doc/user/group/index.md index d1072ecb17e..912c7721d29 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -608,15 +608,14 @@ To ensure only people from your organization can access particular resources, you can restrict access to groups by IP address. This group-level setting applies to: -- The GitLab UI, including subgroups, projects, and issues. +- The GitLab UI, including subgroups, projects, issues, and pages. - [In GitLab 12.3 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/12874), the API. +- Using Git over SSH on GitLab.com. ### Security implications You should consider some security implications before configuring IP address restrictions. -- Restricting HTTP traffic on GitLab.com with IP address restrictions causes SSH requests (including Git operations over - SSH) to fail. For more information, see [the relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/271673). - Administrators and group owners can access group settings from any IP address, regardless of IP restriction. However: - Groups owners cannot access projects belonging to the group when accessing from a disallowed IP address. - Administrators can access projects belonging to the group when accessing from a disallowed IP address. diff --git a/doc/user/ssh.md b/doc/user/ssh.md index 27bb7124afe..e884d762379 100644 --- a/doc/user/ssh.md +++ b/doc/user/ssh.md @@ -354,7 +354,7 @@ can do this by using the command in the [previous topic](#use-different-keys-for However, even if you set `IdentitiesOnly` to `yes`, you cannot sign in if an `IdentityFile` exists outside of a `Host` block. -Instead, you can assign aliases to hosts in the `~.ssh/config` file. +Instead, you can assign aliases to hosts in the `~/.ssh/config` file. - For the `Host`, use an alias like `user_1.gitlab.com` and `user_2.gitlab.com`. Advanced configurations |