Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'} |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
|
comes with a self-signed certificate from
, Inc. To install the CA-signed certificate, follow the steps mentioned below:
- Obtain the certificate from a CA vendor like GoDaddy or Symantec. For more information on how to obtain a CA certificate, see
https://www.godaddy.com/help/nginx-generate-csrs-certificate-signing-requests-3601 or https://knowledge.symantec.com/support/mpki-for-ssl-support/index?page=content&actpl=CROSSLINK&id=SO12398DigiCert. Overwrite the existing certificate files in the scc-build/nginx/ssl.d directory with the files received from the vendor.
Tip |
---|
|
Ensure that the files have include the same previous name as they did before: server.key server.crt |
Copy the local files into the running container. They will persist in a Docker volume.
Code Block |
---|
docker cp /opt/scc-build/nginx/ssl.d/server.key |
nginx:/etc/nginx/ssl.d/server.key |
docker cp /opt/scc-build/nginx/ssl.d/server.crt |
nginx:/etc/nginx/ssl.d/server.crt |
Restart the NGINX container for your changes to go into effect:
nginx