nodeSolidServer / nodeSolidServer/node-solid-server

Authorization options

Open
#1,240 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

Please describe what you did in reproducible steps

In the new Authorization dialog in NSS 5.1.4, there are 4 options that can be selected which equate to different application 'modes':

  1. Read all documents in the Pod (Read)
  2. Add data to existing documents, and create new documents (Write)
  3. Modify and delete data in existing documents, and delete documents (Append)
  4. Give other people and apps access to the Pod, or revoke their (and your) access (Control)

So my questions/comments:

  • Reading these options, it seems that 2) is a combination of Create and Update, and 3) is a combination of Update and Delete. Why can't a user be set to only have Update access?
  • This trusted app information is written to a user's public profile. Seems like this is not information that should be shared publicly. For example, I would not want to publicise that I use an app that is related to a specific medical condition, or an illegal activity. Is there a more appropriate place this information can be written as it should not be public information.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the Authorization dialog behavior described for NSS 5.1.4 and trace where trusted-app information is stored in the public profile. Clarify with maintainers whether Update-only access is required and where authorization metadata should live; done means both decisions are documented and the agreed behavior is implemented.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.