Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Resource Owner restricting their own access

Open
  • Is something wrong?
#256 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
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
authorization, documentation

Research direction

Start by clarifying the use cases for a Resource Owner restricting their own access and review the Authorization Agent primer. Then inspect sai-js to determine how existing Social Agent registrations and delegated grants are handled. Done means the intended behavior is documented and the affected implementation is updated accordingly.

Written by the indexing model from the issue text.

Description

data-authorization

I recall various conversations about scenarios where the user would like to restrict their own access. While specification doesn't seem to prevent Resource Owner from creating Social Agent registration for oneself. At least in sai-js, currently we don't check if it exists and if it does delegate those grants to applications rather than create direct data grants.

If we clarify use cases where such functionality is expected. We should at least mention them in the Authorization Agent primer and update implementations (at least sai-js).

Of course, being a Resource Owner one can always escalate one's own privilege, still in some scenarios having that chmod like step required can prevent some unexpected results.

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

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.