Skip to content

[v13] Allow for Windows PKI operations to target a different domain#33276

Merged
zmb3 merged 1 commit intobranch/v13from
bot/backport-33218-branch/v13
Oct 13, 2023
Merged

[v13] Allow for Windows PKI operations to target a different domain#33276
zmb3 merged 1 commit intobranch/v13from
bot/backport-33218-branch/v13

Conversation

@zmb3
Copy link
Copy Markdown
Collaborator

@zmb3 zmb3 commented Oct 10, 2023

Backport #33218 to branch/v13

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 zmb3 added this pull request to the merge queue Oct 13, 2023
Merged via the queue into branch/v13 with commit eda3b85 Oct 13, 2023
@zmb3 zmb3 deleted the bot/backport-33218-branch/v13 branch October 13, 2023 14:46
@camscale camscale mentioned this pull request Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants