TLS for name owners: add "Multiple TLS Servers Sharing One CA" example#756
Open
mstrofnone wants to merge 1 commit into
Open
TLS for name owners: add "Multiple TLS Servers Sharing One CA" example#756mstrofnone wants to merge 1 commit into
mstrofnone wants to merge 1 commit into
Conversation
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
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.
Adds a new worked example
## Example: Multiple TLS Servers Sharing One CAtodocs/name-owners/tls/index.md, inserted between the existing "Issuing a TLS Certificate for a Subdomain" section and the "Issuing a Subordinate CA Certificate for a Subdomain" section.The existing "Subdomain" example documents the mechanics of
-parent-chain+-parent-key, but doesn't actually walk through the multi-server case that bullet point #2 of Concepts mentions:This new section spells that out concretely with three machines (apex, api, relay), shows the one-time CA creation, then the three
ncgencert -host <fqdn> -parent-chain … -parent-key …invocations, and points the reader at the subordinate-CA section for the third-party-operator case.Purely additive. No other content is changed.