diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-18 00:11:06 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-18 00:11:06 +0000 |
| commit | 90e7f31698f6d67da00ed3a68a7392127746ced2 (patch) | |
| tree | 8e537deb71b944bd0549454a7e2c68be61473fff /doc/administration/gitaly/configure_gitaly.md | |
| parent | 613fdca844c869a6404682ce983512b34f4ea114 (diff) | |
| download | gitlab-ce-90e7f31698f6d67da00ed3a68a7392127746ced2.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/gitaly/configure_gitaly.md')
| -rw-r--r-- | doc/administration/gitaly/configure_gitaly.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/administration/gitaly/configure_gitaly.md b/doc/administration/gitaly/configure_gitaly.md index f6bf563b8cd..e4aef2db9a8 100644 --- a/doc/administration/gitaly/configure_gitaly.md +++ b/doc/administration/gitaly/configure_gitaly.md @@ -555,12 +555,15 @@ Additionally, the certificate (or its certificate authority) must be installed o - Gitaly servers. - Gitaly clients that communicate with it. -Note the following: +### Certificate requirements - The certificate must specify the address you use to access the Gitaly server. You must add the hostname or IP address as a Subject Alternative Name to the certificate. - You can configure Gitaly servers with both an unencrypted listening address `listen_addr` and an encrypted listening address `tls_listen_addr` at the same time. This allows you to gradually transition from unencrypted to encrypted traffic if necessary. +- The certificate's Common Name field is ignored. + +### Configure Gitaly with TLS To configure Gitaly with TLS: |