boulder/wfe2
Aaron Gable f86f88d563
Include supported algs in badSignatureAlgorithm problem doc (#8170)
Add an "algorithms" field to all problem documents, but tag it so it
won't be included in the serialized json unless populated. Populate it
only when the problem type is "badSignatureAlgorithm", as specified in
RFC 8555 Section 6.2.

The resulting problem document looks like this:
```json
{
    "type": "urn:ietf:params:acme:error:badSignatureAlgorithm",
    "detail": "Unable to validate JWS :: JWS signature header contains unsupported algorithm
 \"RS512\", expected one of [RS256 ES256 ES384 ES512]",
    "status": 400,
    "algorithms": [
        "RS256",
        "ES256",
        "ES384",
        "ES512"
    ]
}
```

Fixes https://github.com/letsencrypt/boulder/issues/8155
2025-05-07 18:29:14 -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 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 Include supported algs in badSignatureAlgorithm problem doc (#8170) 2025-05-07 18:29:14 -07:00
wfe_test.go core: Remove DnsNames from Order (#8108) 2025-04-08 15:17:18 -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.