solid / solid/data-interoperability-panel
Authorization Agent URI should be distinct for each user
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
We discussed it shortly during the call today. Authorization Agent provider, for each user they serve would just need create distinct URI which would identify Authorization Agent (instance?) of that user.
It would come useful in keeping Agent Registration discovery simple. If AA URI is shared, there would need to be additional information in request to disambiguate registration created by which user is being discovered.
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
Review the Authorization Agent provider and Agent Registration discovery behavior described in this issue. Determine whether each served user needs a distinct Authorization Agent URI and how shared URIs would affect discovery requests. Done means the specification records an agreed URI model and its impact on registration discovery.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100