Should we restrict Social Agent Reigstration discovery to AA of that social agent?

Open
#252 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
authorization, security

Research direction

No file, test, or entry point is named. Start by locating the Social Agent Registration discovery rules and the definitions of the End-user, social agent, and authorisation agent in the specification. Done means resolving whether discovery is restricted and recording the decided access rule in the relevant specification text.

Written by the indexing model from the issue text.

Description

Currently, any application acting on behalf of the End-user (social agent) would be able to discover social agent registrations created for them by other agents (starting from WebID of those agents). Should we restrict it to only AA of that social agent?

Dominant language
Bikeshed
Stars
58
Forks
18
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from solid/data-interoperability-panel

All issues in solid/data-interoperability-panel

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.