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