Skip to content

Updating cert titles and links in the MTLS page #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 23, 2024
Merged

Updating cert titles and links in the MTLS page #102

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ccec46b
updating cert titles and links
subrama6 Feb 23, 2024
c54dfcf
updating MTLS page to reference Cert page
subrama6 Feb 23, 2024
5a4b44d
pr feedback
subrama6 Feb 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/webhooks/03-Mutual-TLS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,10 @@ These steps assume you already have server authentication setup.

In general, there are five steps needed to turn on client authentication for your server:

1. Download the PEM version of the [DigiCert Global Root CA](https://cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem) certificate.
1. Download the PEM version of the DigiCert Root certificate from our [Public Certificates Page](../../docs/webhooks/08-Certificates.md).
2. Turn on client certificate verification.
3. Specify the CA certificate from step 1 as trusted.
4. Set the verification depth to 2 since our PagerDuty certificate is actually signed by the [DigiCert SHA2 Secure Server CA](https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt) which is an intermediate CA under DigiCert Global Root CA.
4. Set the verification depth to 2 since our PagerDuty certificate is actually signed by an intermediate.
5. Verify the client certificate is actually from PagerDuty by inspecting its Subject Domain Name.

Now we will go over sample server configurations for NGINX and Apache.
Expand Down