create option to return all certs from signer in SCEP response #2307
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
…esponse creation of ReturnEntireCertChain option for SCEP provisioner which controls whether to use the default behavior of just returning the leaf cert or to return all certificates that we get from the signer response
github-actions
bot
added
the
needs triage
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.
creation of ReturnEntireCertChain option for SCEP provisioner which controls whether to use the current default behavior of just returning the leaf cert or to return all certificates that we get from the signer response
Name of feature:
ReturnEntireCertChainPain or issue this feature alleviates:
Currently, the SCEP response does not contain the entire intermediate chain that the CA provides in response to the CSR. The CA may return the leaf certificate in addition to intermediate certificates from which it is signed in order to build a chain of trust to the common root which is in both server and client stores.
Why is this important to the project (if not answered above):
Without this feature, clients must have the intermediate certificates manually managed in their trust stores which introduces failure points for administration and can cause outages during rotations
Is there documentation on how to use this feature? If so, where?
In what environments or workflows is this feature supported?
In what environments or workflows is this feature explicitly NOT supported (if any)?
Supporting links/other PRs/issues:
💔Thank you!