Allow for Windows PKI operations to target a different domain#33218
Merged
Allow for Windows PKI operations to target a different domain#33218
Conversation
ibeckermayer
approved these changes
Oct 10, 2023
Contributor
ibeckermayer
left a comment
ibeckermayer
left a comment
There was a problem hiding this comment.
Worthy of a docs update?
Collaborator
Author
Yep, 100%. Will do it separately. |
rosstimothy
approved these changes
Oct 10, 2023
public-teleport-github-review-bot
Bot
removed the request for review
from gzdunek
Today, our AD support largely assumes there is a single active directory domain. The certificates that we generate are for users in this domain, the computers we discover via LDAP come from this domain, and the PKI set up we perform targets this domain. In more complicated AD configurations, PKI is often configured in a root domain, while users, servers, and discovery should be done against a child domain. The new pki_domain configuration field will allow you to override the default domain specified in the ldap section with a root domain that is used for configuring the NTAuth store and publishing the CRL. Teleport continues to do discovery and issue certificates for the domain specified in the ldap section of the config.
zmb3
force-pushed
the
zmb3/pki-domain-2
branch
from
0f5ebd8 to
4b73fb0
Compare
This was referenced Oct 10, 2023
zmb3
added a commit
that referenced
this pull request
Oct 11, 2023
This documents the changes in #33218
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Oct 11, 2023
This documents the changes in #33218
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 11, 2023
This documents the changes in #33218
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 11, 2023
This documents the changes in #33218
zmb3
added a commit
that referenced
this pull request
Oct 11, 2023
This documents the changes in #33218
This was referenced Oct 11, 2023
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Oct 19, 2023
This documents the changes in #33218
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Oct 19, 2023
This documents the changes in #33218
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Today, our AD support largely assumes there is a single active directory domain. The certificates that we generate are for users in this domain, the computers we discover via LDAP come from this domain, and the PKI set up we perform targets this domain.
In more complicated AD configurations, PKI is often configured in a root domain, while users, servers, and discovery should be done against a child domain.
The new pki_domain configuration field will allow you to override the default domain specified in the ldap section with a root domain that is used for configuring the NTAuth store and publishing the CRL. Teleport continues to do discovery and issue certificates for the domain specified in the ldap section of the config.