Skip to content

Commit d4ad7b8

Browse files
authored
Update certificate export instructions for clarity
Clarify the requirement for Base64-encoded PEM files in the instructions for exporting certificates.
1 parent cd0c28b commit d4ad7b8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/pipelines/agents/certificate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ console.log(tls.rootCertificates.join("\n"));
143143

144144
The `NODE_EXTRA_CA_CERTS` environment variable, introduced in Node v7.3.0, allows you to specify a file that contains one or more CA certificates that Node trusts (in addition to the default bundle). `NODE_EXTRA_CA_CERTS` appends to the trust store.
145145

146-
1. On your server or CA, export the root (and any intermediate, if needed) certificates as a PEM-encoded file. This format is a text file with `-----BEGIN CERTIFICATE-----` and Base64 data. Make sure that you use Base64-encoded PEM, and not DER. (On Windows, .cer files can be either; you can rename to .pem to avoid confusion. The file can actually have any extension, but .pem or .crt is standard.)
146+
1. On your server or CA, export the root (and any intermediate, if needed) certificates as a PEM-encoded file. This format is a text file with `-----BEGIN CERTIFICATE-----` and Base64 data. Make sure that you use a Base64-encoded PEM file, and not a DER file. (On Windows, .cer files can be either; you can rename to .pem to avoid confusion. The file can actually have any extension, but .pem or .crt is standard.)
147147

148148
If you have multiple internal CAs (a chain), you can concatenate them into one file. Node reads all certificates in that file.
149149

0 commit comments

Comments
 (0)