nodeSolidServer / nodeSolidServer/node-solid-server
Authorization options
未关闭
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 1.8k
- 派生
- 308
- PR 合并指标
- 30 天内没有已合并 PR
描述
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':
- Read all documents in the Pod (Read)
- Add data to existing documents, and create new documents (Write)
- Modify and delete data in existing documents, and delete documents (Append)
- 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.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
先复现 NSS 5.1.4 所描述的 Authorization dialog 行为,并追踪受信任应用信息存储在 public profile 的什么位置。与维护者确认是否需要 Update-only access,以及授权元数据应存放在哪里;当两项决定都已记录并且约定的行为已实现时,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript
- 领域
- authorization, security
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100