boulder/wfe2
Aaron Gable e398c4d1ec
Clearer error message when goodkey fails unexpectedly (#7642)
This will prevent users from believing their key is at fault when the
actual error is between Boulder and the database.

Fixes https://github.com/letsencrypt/boulder/issues/7624
2024-08-06 09:23:06 -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
stale.go Finish migration from int64 timestamps to timestamppb (#7142) 2023-11-27 13:37:31 -08:00
stale_test.go Finish migration from int64 timestamps to timestamppb (#7142) 2023-11-27 13:37:31 -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 WFE: Reject new orders containing paused identifiers (#7599) 2024-07-25 13:46:40 -04:00
wfe_test.go RA: pass through unpause requests to SA (#7630) 2024-07-25 16:34:02 -04: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.