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
7f8fc64edc9c
Commit
7f8fc64edc9c
authored
1 year ago
by
Achilleas Pipinellis
Browse files
Options
Downloads
Patches
Plain Diff
Add note to install custom public certificates to all nodes
parent
ced3f2d1c778
No related branches found
Branches containing commit
No related tags found
Tags containing commit
3 merge requests
!102
heptapod#1237: making 0.38 the new oldstable
,
!96
Merged heptapod branch for upstream 15.11 in heptapod-stable
,
!93
Merged upstream 15.11.0+rc42+ce.0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/settings/ssl/index.md
+9
-5
9 additions, 5 deletions
doc/settings/ssl/index.md
with
9 additions
and
5 deletions
doc/settings/ssl/index.md
+
9
−
5
View file @
7f8fc64e
...
...
@@ -539,5 +539,5 @@
## Install custom public certificates
Some environments connect to external resources for various tasks
. Omnibus
GitLab
Some environments connect to external resources for various tasks
and
GitLab
allows these connections to use HTTPS, and supports connections with self-signed certificates.
...
...
@@ -543,2 +543,6 @@
allows these connections to use HTTPS, and supports connections with self-signed certificates.
GitLab has its own ca-cert bundle that you can add certs to by placing the
individual custom certs in the
`/etc/gitlab/trusted-certs`
directory. They then
get added to the bundle. They are added using openssl's
`c_rehash`
method, which
only works on a
[
single certificate
](
#using-a-custom-certificate-chain
)
.
...
...
@@ -544,5 +548,5 @@
Omnibus
GitLab ships with the official
[
CAcert.org
](
http://www.cacert.org/
)
GitLab ships with the official
[
CAcert.org
](
http://www.cacert.org/
)
collection of trusted root certification authorities which are used to verify
certificate authenticity.
...
...
@@ -555,6 +559,7 @@
To install custom public certificates:
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.
1.
Copy only the public certificate file into the
`/etc/gitlab/trusted-certs`
directory.
If you have a multi-node installation, make sure to copy the certificate in all nodes.
-
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
...
...
@@ -559,6 +564,6 @@
-
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`
.
`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.
...
...
@@ -566,7 +571,6 @@
To specify a different path and file name, you can
[
change the default SSL certificate location
](
#change-the-default-ssl-certificate-location
)
.
1.
[
Enable and manually configure HTTPS on NGINX
](
#configure-https-manually
)
to set up GitLab to use your own certificates.
1.
Reconfigure GitLab:
```
shell
...
...
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