Skip to content

[v12] Fix link to CA Pinning information #26689

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
ptgott merged 1 commit into from
May 22, 2023
Merged

[v12] Fix link to CA Pinning information #26689

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 7 additions & 5 deletions docs/pages/management/operations/ca-rotation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,15 @@ description: How to rotate Teleport's certificate authority

- (!docs/pages/includes/tctl.mdx!)

## Certificate Authority rotation
## Certificate authority rotation

This section will show you how to implement certificate rotation in practice.
This section will show you how to rotate Teleport's certificate authority.

If you are using [CA Pinning](../join-services-to-your-cluster/join-token.mdx#obtain-a-ca-pin)
when adding new nodes, the CA pin will change after the rotation. Make sure you
use the *new* CA pin when adding nodes after rotation.
If you are joining Teleport processes to a cluster via the Teleport Auth Service
using a [join token](../join-services-to-your-cluster/join-token.mdx), each
Teleport process will need a CA pin to trust the Auth Service. The CA pin will
change after each CA rotation. Make sure you use the *new* CA pin when adding
Teleport services after rotation.

<Admonition type="warning" title="Desktop Access">
Teleport signs Windows Desktop certificates with the user certificate authority.
Expand Down