ARAP: bound retry and polling when no expiry is supplied
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- api, documentation
Research direction
Read the retry, polling, and expiry rules for ARAP, especially the optional approved_until, task.expires_at, and the durable state described in #741 on main; also consult #663 and #745 for scope and independence. Determine which expiry governs each operation and what fallback deadlines or finite attempt budgets the specification should require across handoff. Done means the normative text clearly defines both bounds, their persistence across processes, and behavior when task.expires_at is absent.
Written by the indexing model from the issue text.
Description
Split out of #663, problem 3.
Problem
Retrying stops "once the approval expires" without saying whether the Approval Result's approved_until or a PDP-returned expiry governs. Polling stops at task.expires_at, which is OPTIONAL, with no rule for its absence, so a naive PEP polls indefinitely.
Recommendation
Name the governing expiry for retries. Give retry and re-request finite attempt budgets. Stop polling at task.expires_at, or at a configured deadline or budget where that member is absent.
Cost
All three bounds MUST survive handoff, which is durable cross-process state, and no baseline value is given, so two conformant PEPs may differ arbitrarily.
Status
#741, on main, independent of #745.
- Dominant language
- TypeScript
- Stars
- 170
- Forks
- 46
- Avg merge
- 18h 5m
- Merged PRs (30d)
- 43
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from openid/authzen
-
Certification Scenario §7.2.2, §7.3.2 and §7.4.2: identical results, or identical fixture results?Possibly taken @alexolivier claimed this 4 days ago. Openauthorization-api certification
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Search interop runner compares results as JSON strings, so member order decides PASS/FAILMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openid/authzen#693 · 3 comments ·
Maintainers usually reply within 1 day
-
certification
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openid/authzen#640 · 1 comment ·
Maintainers usually reply within 1 day
-
access-requests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openid/authzen#578 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
remotion-dev/remotion#12905 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
supermomonga/paseo-plugin-zcode-provider#83 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
oxidecomputer/skepsis#102 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
voidzero-dev/void#677 ·
Maintainers usually reply within 1 day