boulder/wfe2
Aaron Gable ebf232cccb
Return updated account object on DeactivateRegistration path (#8060)
Update the SA to re-query the database for the updated account after
deactivating it, and return this to the RA. Update the RA to pass this
value through to the WFE. Update the WFE to return this value, rather
than locally modifying the pre-deactivation account object, if it gets
one (for deployability).

Also remove the RA's requirement that the request object specify its
current status so that the request can be trimmed down to just an ID.
This proto change is backwards-compatible because the new
DeactivateRegistrationRequest's registrationID field has the same type
(int64) and field number (1) as corepb.Registration's id field.

Part of https://github.com/letsencrypt/boulder/issues/5554
2025-03-14 14:17:42 -07:00
..
README.md Duplicate WFE to WFE2. (#2839) 2017-07-05 13:32:45 -07:00
cache.go Add account cache to WFE (#5855) 2021-12-15 11:10:23 -08:00
cache_test.go Add account cache to WFE (#5855) 2021-12-15 11:10:23 -08:00
stats.go WFE: Count NewOrders which indicate replacement (#7416) 2024-04-08 12:32:45 -04:00
verify.go Clearer error message when goodkey fails unexpectedly (#7642) 2024-08-06 09:23:06 -07:00
verify_test.go KeyPolicy: add custom constructor and make all fields private (#7543) 2024-06-18 17:52:50 -04:00
wfe.go Return updated account object on DeactivateRegistration path (#8060) 2025-03-14 14:17:42 -07:00
wfe_test.go Return updated account object on DeactivateRegistration path (#8060) 2025-03-14 14:17:42 -07:00

README.md

WFE v2

The wfe2 package is copied from the wfe package in order to implement the "ACME v2" API. This design choice was made to facilitate a clean separation between v1 and v2 code and to support running a separate API process on a different port alongside the v1 API process.