mirror of
https://github.com/goharbor/harbor.git
synced 2024-11-27 20:59:10 +01:00
120 lines
4.6 KiB
Markdown
120 lines
4.6 KiB
Markdown
# Configuring Harbor with HTTPS Access
|
|
|
|
Because Harbor does not ship with any certificates, it uses HTTP by default to serve registry requests. However, it is highly recommended that security be enabled for any production environment. Harbor has an Nginx instance as a reverse proxy for all services, you can use the prepare script to configure Nginx to enable https.
|
|
|
|
## Getting a certificate
|
|
|
|
Assuming that your registry's **hostname** is **reg.yourdomain.com**, and that its DNS record points to the host where you are running Harbor. You first should get a certificate from a CA. The certificate usually contains a .crt file and a .key file, for example, **yourdomain.com.crt** and **yourdomain.com.key**.
|
|
|
|
In a test or development environment, you may choose to use a self-signed certificate instead of the one from a CA. The below commands generate your own certificate:
|
|
|
|
1) Create your own CA certificate:
|
|
|
|
```
|
|
openssl req \
|
|
-newkey rsa:4096 -nodes -sha256 -keyout ca.key \
|
|
-x509 -days 365 -out ca.crt
|
|
```
|
|
2) Generate a Certificate Signing Request:
|
|
|
|
If you use FQDN like **reg.yourdomain.com** to connect your registry host, then you must use **reg.yourdomain.com** as CN (Common Name).
|
|
Otherwise, if you use IP address to connect your registry host, CN can be anything like your name and so on:
|
|
|
|
```
|
|
openssl req \
|
|
-newkey rsa:4096 -nodes -sha256 -keyout yourdomain.com.key \
|
|
-out yourdomain.com.csr
|
|
```
|
|
3) Generate the certificate of your registry host:
|
|
|
|
If you're using FQDN like **reg.yourdomain.com** to connect your registry host, then run this command to generate the certificate of your registry host:
|
|
|
|
```
|
|
openssl x509 -req -days 365 -in yourdomain.com.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out yourdomain.com.crt
|
|
```
|
|
If you're using **IP**, say **192.168.1.101** to connect your registry host, you may instead run the command below:
|
|
|
|
```
|
|
echo subjectAltName = IP:192.168.1.101 > extfile.cnf
|
|
|
|
openssl x509 -req -days 365 -in yourdomain.com.csr -CA ca.crt -CAkey ca.key -CAcreateserial -extfile extfile.cnf -out yourdomain.com
|
|
.crt
|
|
```
|
|
## Configuration and Installation
|
|
After obtaining the **yourdomain.com.crt** and **yourdomain.com.key** files,
|
|
you can put them into directory such as ```/root/cert/```:
|
|
|
|
```
|
|
cp yourdomain.com.crt /root/cert/
|
|
cp yourdomain.com.key /root/cert/
|
|
```
|
|
|
|
|
|
Next, edit the file make/harbor.cfg , update the hostname and the protocol, and update the attributes ```ssl_cert``` and ```ssl_cert_key```:
|
|
|
|
```
|
|
#set hostname
|
|
hostname = reg.yourdomain.com
|
|
#set ui_url_protocol
|
|
ui_url_protocol = https
|
|
......
|
|
#The path of cert and key files for nginx, they are applied only the protocol is set to https
|
|
ssl_cert = /root/cert/yourdomain.com.crt
|
|
ssl_cert_key = /root/cert/yourdomain.com.key
|
|
```
|
|
|
|
Generate configuration files for Harbor:
|
|
|
|
```
|
|
./prepare
|
|
```
|
|
|
|
If Harbor is already running, stop and remove the existing instance. Your image data remain in the file system
|
|
|
|
```
|
|
docker-compose down
|
|
```
|
|
Finally, restart Harbor:
|
|
|
|
```
|
|
docker-compose up -d
|
|
```
|
|
After setting up HTTPS for Harbor, you can verify it by the following steps:
|
|
|
|
1. Open a browser and enter the address: https://reg.yourdomain.com . It should display the user interface of Harbor.
|
|
|
|
2. On a machine with Docker daemon, make sure the option "-insecure-registry" does not present, and you must copy ca.crt generated in the above step to /etc/docker/certs.d/reg.yourdomain.com(or your registry host IP), if the directory does not exist, create it.
|
|
If you mapped nginx port 443 to another port, then you should instead create the directory /etc/docker/certs.d/reg.yourdomain.com:port(or your registry host IP:port). Then run any docker command to verify the setup, e.g.
|
|
|
|
```
|
|
docker login reg.yourdomain.com
|
|
```
|
|
If you've mapped nginx 443 port to another, you need to add the port to login, like below:
|
|
|
|
```
|
|
docker login reg.yourdomain.com:port
|
|
```
|
|
|
|
## Troubleshooting
|
|
1. You may get an intermediate certificate from a certificate issuer. In this case, you should merge the intermediate certificate with your own certificate to create a certificate bundle. You can achieve this by the below command:
|
|
|
|
```
|
|
cat intermediate-certificate.pem >> yourdomain.com.crt
|
|
```
|
|
2. On some systems where docker daemon runs, you may need to trust the certificate at OS level.
|
|
On Ubuntu, this can be done by below commands:
|
|
|
|
```sh
|
|
cp youdomain.com.crt /usr/local/share/ca-certificates/reg.yourdomain.com.crt
|
|
update-ca-certificates
|
|
```
|
|
|
|
On Red Hat (CentOS etc), the commands are:
|
|
|
|
```sh
|
|
cp yourdomain.com.crt /etc/pki/ca-trust/source/anchors/reg.yourdomain.com.crt
|
|
update-ca-trust
|
|
```
|
|
|
|
|