forked from letsencrypt/boulder
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make POSTing KeyAuthorization optional, V2 don't echo it. (letsencryp…
…t#3526) This commit updates the RA to make the notion of submitting a KeyAuthorization value as part of the ra.UpdateAuthorization call optional. If set, the value is enforced against expected and an error is returned if the provided authorization isn't correct. If it isn't set the RA populates the field with the computed authorization for the VA to enforce against the value it sees in challenges. This retains the legacy behaviour of the V1 API. The V2 API will never unmarshal a provided key authorization. The ACMEv2/WFEv2 prepChallengeForDisplay function is updated to strip the ProvidedKeyAuthorization field before sending the challenge object back to a client. ACMEv1/WFEv1 continue to return the KeyAuthorization in challenges to avoid breaking clients that are relying on this legacy behaviour. For deployability ease this commit retains the name of the core.Challenge.ProvidedKeyAuthorization field even though it should be called core.Challenge.ComputedKeyAuthorization now that it isn't set based on the client's provided key authz. This will be easier as a follow-up change. Resolves letsencrypt#3514
- Loading branch information
Showing
6 changed files
with
75 additions
and
26 deletions.
There are no files selected for viewing
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
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
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
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
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
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