What form should capability values take?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing-qa
Research direction
Start by reading specification sections 8.2.1, 9.1.2, and 12.1.3–12.4, then inspect the suite’s capability validation described in the issue. Resolve the intended URN form and interim advertising policy with the working group before changing the checks. Done means the specification and suite agree on accepted capability values and metadata names.
Written by the indexing model from the issue text.
Description
capabilities: OPTIONAL. JSON array containing a list of registered IANA URNs referencing PDP specific capabilities. (spec §9.1.2)
This specification asks IANA to register a new URN sub-namespace within the "IETF URN Sub-namespace for Registered Protocol Parameter Identifiers" registry defined in [RFC3553]. Registry Name: authzen […] Repository: "AuthZEN Policy Decision Point Capabilities" registry (Section 12.3 of [This Document]) (spec §12.4)
Furthermore, the PDP MUST declare support for the corresponding capability URN in its supported_capabilities metadata (Section 9.1.2). (spec §8.2.1)
Conflicts and gaps.
- The URN form. §12.4 implies registered capability URNs of the form
urn:ietf:params:authzen:<name>, but the registry has no entries. The Cerbos certification PDP, from the scenario's author, advertisesurn:authzen:pdp:core:v1,urn:authzen:pdp:pagination:v1and four similar values.authzenis not a registered URN namespace. - The member name. §8.2.1 calls the metadata member
supported_capabilities; §9.1.2 and the registry (§12.1.3) call itcapabilities. #653 corrects this.
Suite today. It requires capabilities to be an array of strings. It warns about values outside urn:ietf:params:authzen:, and about any metadata member outside the registry, such as supported_capabilities.
Questions.
- Is
urn:ietf:params:authzen:<name>the intended form? Will the WG register capabilities (for example pagination and the evaluation options) before certification starts? - Until then, should a PDP advertise capabilities at all? If so, should the suite accept any URN?
- Dominant language
- TypeScript
- Stars
- 171
- Forks
- 46
- Avg merge
- 3h 29m
- Merged PRs (30d)
- 38
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 7 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 2/5 1-3 hours Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
unwrapDatabaseError masks real DB errors with TypeError: Cannot convert object to primitive valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NEARBuilders/everything-dev#798 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/durable-harness#53 ·
Maintainers usually reply within 1 day
-
[Bug]: Redesign tab bars ignore clicks on Linux: hidden chat layers keep window drag regionsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
experiência: a doc manda subir para o Micro do Supabase, mas não diz que exige plano pago nem quanto custaPossibly taken A pull request linked to this issue is open or already merged. Openarea/docs area/ui enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
melgarafael/DeskcommCRM#4098 ·
Maintainers usually reply within 1 day
-
dependencies platform: ios
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
software-mansion/react-native-executorch#1617 ·
Maintainers usually reply within 1 day