boulder/wfe2
Aaron Gable d7e4ed18ad
Remove the last vestiges of account contacts (#8247)
Remove the concept of an account contact from all of boulder except the
WFE. Specifically:
- Delete the UpdateRegistrationContact methods from the RA and SA
- Remove all understanding of the Contact field from the RA and SA's
NewRegistration methods
- Remove the Contact field from corepb.Registration to ensure it can
never be communicated anywhere

Note that this does not remove the Contact field from core.Registration,
as that represents an ACME API type, and we're still willing to parse
the Contact field from incoming new-account requests.

Fixes https://github.com/letsencrypt/boulder/issues/8199
2025-07-03 12:55:16 -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 Remove the last vestiges of account contacts (#8247) 2025-07-03 12:55:16 -07:00
stats.go WFE: Count NewOrders which indicate replacement (#7416) 2024-04-08 12:32:45 -04:00
verify.go wfe: Separately handle badSignature at JWS parse time (#8091) 2025-04-08 15:45:06 -07:00
verify_test.go wfe: Separately handle badSignature at JWS parse time (#8091) 2025-04-08 15:45:06 -07:00
wfe.go RFC 9773: Update ARI URL (#8274) 2025-06-26 08:50:44 -07:00
wfe_test.go Remove the last vestiges of account contacts (#8247) 2025-07-03 12:55:16 -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.