nodeSolidServer / nodeSolidServer/node-solid-server
confirmation for change in pod parameters
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
To avoid change of control some changes shall be closely supervised :
- user email
- IdP provider
- owner
- external webId
Among possibilities are :
- ask confirmation by email : email is not a MUST actually
- have a secure resource box where to check for new values where only owner has access
actually NSS uses .meta,
inconvenient it is discoverable in container representation, but all values are actually public)
Contributor guide
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
The issue does not name files, tests, or an entry point. Start by tracing how pod parameters such as the user email, IdP provider, owner, and external webId are changed, then define the confirmation and private-resource requirements with the project maintainers. Done means an agreed mechanism prevents unsupervised changes and its security behavior is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100