confirmation for change in pod parameters

Open
#1,681 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js

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.

Description

enhancement

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)
Dominant language
JavaScript
Stars
1.8k
Forks
308
PR merge metrics
No merged PRs in 30d

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.

More from nodeSolidServer/node-solid-server

All issues in nodeSolidServer/node-solid-server

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.