Core 5.6.2 - chaining Distributed Claims
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start by locating section 5.6.2, “Distributed Claims,” in the Connect specification and read the surrounding explanation and examples. Clarify whether a Claims Provider may delegate to another Claims Provider using Distributed Claims, or whether Aggregated Claims are required. Done means the section explicitly resolves this delegation path.
Written by the indexing model from the issue text.
Description
Originally submitted by p_kowalik (Pawel Kowalik) on 2019-05-17
In the sections 5.6.2 about Distributed Claims it is not clear, whether Claims Provider can further delegate claims to yet another Claims Provider by using same mechanism of Distributed Claims or embed Aggregated Claims.
Would be beneficial to add some language around it.
Bitbucket status: open
Bitbucket origin: issue 1086
- Dominant language
- No language data
- Stars
- 3
- Forks
- 3
- Avg merge
- 20h 14m
- Merged PRs (30d)
- 1
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.
More from openid/connect
-
component: Core migrated-from-bitbucket priority: major type: bug
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
migrated-from-bitbucket priority: minor type: task
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
component: Assurance migrated-from-bitbucket priority: major type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
component: Core migrated-from-bitbucket priority: major type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100