9181
66%

Ran 11 May 2018 08:14PM UTC

Jobs 1

Files 85

Run time 6s

Badge

Embed ▾

pending completion

Build # 9181

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

WFE2: Allow legacy Key ID prefix for ACME v2 JWS. (#3705)

While we intended to allow legacy ACME v1 accounts created through the WFE to work with the ACME v2 implementation and the WFE2 we neglected to consider that a legacy account would have a Key ID URL that doesn't match the expected for a V2 account. This caused `wfe2/verify.go`'s `lookupJWK` to reject all POST requests authenticated by a legacy account unless the ACME client took the extra manual step of "fixing" the URL.

This PR adds a configuration parameter to the WFE2 for an allowed legacy key ID prefix. The WFE2 verification logic is updated to allow both the expected key ID prefix and the configured legacy key ID prefix. This will allow us to specify the correct legacy URL in configuration for both staging/prod to allow unmodified V1 ACME accounts to be used with ACME v2.

Resolves https://github.com/letsencrypt/boulder/issues/3674

Run Details

10037 of 16047 relevant lines covered (62.55%)

0.69 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
9	9181.9 (RUN="coverage")	11 May 2018 08:14PM UTC	0	62.55	Travis Job 9181.9

Source Files on build 9181

Detailed source file information is not available for this build.

letsencrypt / boulder / 9181
66%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 9181

letsencrypt / boulder / 9181 66%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 9181

letsencrypt / boulder / 9181
66%

README BADGES
x