letsencrypt / letsencrypt/pebble
Expired Authorizations/Challenges are still pending
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
If an Authorization has expired, loading it will show a "pending" status.
If a Challenge belongs to an Authorization which has expired, loading it will show a "pending" status.
Triggering the expired Challenge will result in an error json payload, as expected, such as:
{u'status': 400, u'type': u'urn:ietf:params:acme:error:malformed', u'detail': u'Authorization expired 2020-02-28T20:25:02Z'}
Attempting to load the Authorization or Challenge after receiving this payload will still return a "pending" status.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported flow by loading an expired Authorization and a Challenge belonging to it, triggering the expired Challenge, then loading both resources again. Trace the state handling for these resources and verify that their responses no longer report "pending" after expiration and the error response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100