By default, Harbor uses its own private key and certificate to authenticate with Docker clients. This topic describes how to optionally customize your configuration to use your own key and certificate.
Harbor requires the Docker client to access the Harbor registry with a token. The procedure to generate a token is like
Docker Registry v2 authentication. Firstly, you make a request to the token service for a token. The token is signed by the private key. After that, you make a new request with the token to the Harbor registry, Harbor registry verifies the token with the public key in the root cert bundle. Then Harbor registry authorizes the Docker client to push and pull images.
If you do not already have a certificate, follow the instructions in
Generate a Root Certificate to generate a root certificate by using openSSL.
Enter information to include in your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN. There are quite a few fields but you can leave some of them blank. For some fields there is a default value. If you enter ., the field is left blank.
Country Name (2 letter code) [AU]:
State or Province Name (full name) [Some-State]:
Locality Name (eg, city) :
Organization Name (eg, company) [Internet Widgits Pty Ltd]:
Organizational Unit Name (eg, section) :
Common Name (eg, server FQDN or YOUR name) :
Email Address :
After you run these commands, the files private_key.pem and root.crt are created in the current directory.