Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
omnibus-heptapod
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
heptapod
omnibus-heptapod
Commits
66e44ac9
Commit
66e44ac9
authored
2 years ago
by
James Reed
Browse files
Options
Downloads
Patches
Plain Diff
Expand on custom public certificate trust usage
parent
497abe49
No related branches found
Branches containing commit
No related tags found
Tags containing commit
2 merge requests
!102
heptapod#1237: making 0.38 the new oldstable
,
!92
Merging upstream 15.10.0+ce.0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/settings/ssl/index.md
+26
-7
26 additions, 7 deletions
doc/settings/ssl/index.md
with
26 additions
and
7 deletions
doc/settings/ssl/index.md
+
26
−
7
View file @
66e44ac9
...
...
@@ -556,9 +556,12 @@
1.
Generate the
**PEM**
or
**DER**
encoded public certificate from your private key certificate.
1.
Copy only the public certificate file in the
`/etc/gitlab/trusted-certs`
directory.
By default, GitLab expects to find a certificate titled after your GitLab domain name with a
`.crt`
extension. For instance, if your server address is
`https://gitlab.example.com`
, the
certificate should be named
`gitlab.example.com.crt`
.
-
When configuring GitLab to use a custom public certificate, by default, GitLab expects to find a certificate named
after your GitLab domain name with a
`.crt`
extension. For example, if your server address is
`https://gitlab.example.com`
, the certificate should be named
`gitlab.example.com.crt`
.
-
If GitLab needs to connect to an external resource that uses a custom public certificate, store the certificate in
the
`/etc/gitlab/trusted-certs`
directory with a
`.crt`
extension. You don't have to name the file based on the
domain name of the related external resource, though it helps to use a consistent naming scheme.
To specify a different path and file name, you can
[
change the default SSL certificate location
](
#change-the-default-ssl-certificate-location
)
.
...
...
@@ -570,10 +573,26 @@
sudo
gitlab-ctl reconfigure
```
WARNING:
If using a custom certificate chain, the root and intermediate certificates must
be put into separate files in
`/etc/gitlab/trusted-certs`
[
due to `c_rehash` creating a hash for the first certificate only
](
https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/1425
)
.
### Using a custom certificate chain
Because of a
[
known issue
](
https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/1425
)
, if using a custom certificate
chain, the root and intermediate certificates
**must**
be put into separate files in the
`/etc/gitlab/trusted-certs`
directory.
This applies in both cases where GitLab itself, or external resources GitLab must connect to, are using a custom
certificate chain.
For example, for GitLab itself you can use:
-
`/etc/gitlab/trusted-certs/example.gitlab.com.crt`
-
`/etc/gitlab/trusted-certs/example.gitlab.com_intermediate.crt`
-
`/etc/gitlab/trusted-certs/example.gitlab.com_root.crt`
For external resources GitLab must to, you can use:
-
`/etc/gitlab/trusted-certs/external-service.gitlab.com.crt`
-
`/etc/gitlab/trusted-certs/external-service.gitlab.com_intermediate.crt`
-
`/etc/gitlab/trusted-certs/external-service.gitlab.com_root.crt`
## Details on how GitLab and SSL work
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment