Allow Tokens for Renewing Certificates #2042
Open
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.
Name of feature: Provide Functionality for Tokens to be Used for Renewing Certificates
Pain or issue this feature alleviates: Currently, a provisioner doesn't allow for tokens to be used in the
provisioner.RenewWithToken
function as the audience is set to use/1.0/sign
, which makes the token invalid for renewing certificates.Why is this important to the project (if not answered above): Renewal of certificates via tokens issued with a provisioner is required for planned application usage.
Is there documentation on how to use this feature? If so, where?
None that I am aware of.
In what environments or workflows is this feature supported?
Any environments where this usage is planned or expected.
In what environments or workflows is this feature explicitly NOT supported (if any)?
None
Supporting links/other PRs/issues: N/A
💔Thank you!