Fixed validation response from acme_accounts #6604
Merged
Conversation
This file contains 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
mattjackson220
added
bug
4 tasks
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.
Closes: #6368
This PR fixes the validation error at the
/acme_accountsendpoint when the private key is empty or missingWhich Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Run TO and
POSTto the/acme_accountsendpoint withprivateKeyeither empty or missing and verify that the response correctly says "privateKey" instead of "private_key"If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist