nodeSolidServer / nodeSolidServer/node-solid-server

Rethink authentication configuration

未關閉
#672 11 則留言 3 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

authentication in progress semver-major
主要語言
JavaScript
星號
1.8k
分支
308
PR 合併指標
30 天內沒有已合併 PR

描述

Right now, the server supports two different auth modes, confusingly named auth: "tls" and auth: "oidc", even though that doesn't cover exactly what they do. The main problem is that this one setting gives the impression that both methods are mutually exclusive, whereas they are not.

Discussions such as #667, #671, https://github.com/solid/solid-auth-client/issues/44, https://github.com/solid/solid/issues/138, https://github.com/solid/oidc-auth-manager/issues/20 show that there is a need for more clarity, and a better configuration option.

This issue tracks general progress and will act as a tracker for multiple sub-issues.
Here are the steps we need to take in my opinion:

  • Have one single contract for the entire node-solid-server to track a) the WebID of the logged-in agent b) the method through which that agents has logged in
  • Document the above contract
  • Ensure that “ask for a client certificate on every resource (WebID-TLS)” can be enabled and disabled independently of other features
  • Ensure that “act as an OIDC identity provider” can be enabled and disabled independently of other features
  • Ensure that “log in with OIDC through username/password” can be enabled and disabled independently of other features
  • Ensure that “log in with OIDC through client certificates (WebID-TLS)” can be enabled and disabled independently of other features
  • Ensure that “accept bearer tokens” can be enabled and disabled independently of other features
  • Examine whether we want to always translate successful logins into an Express cookie-based session
  • Examine whether we want to allow turning on or off cookie-based sessions
  • Create a configuration section that allows to enable and disable all of the above options independently
  • Update the init generator to create the right config
  • Remove the old auth config section

Feedback welcome.

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

先閱讀討論 #667、#671 以及連結的身分驗證 issues,以了解尚未解決的設計。接著追蹤現有的 auth 設定和 init generator,兩者都在 issue 中提到。完成的標準是:以針對所列登入、token、憑證、identity provider 和 cookie-session 選項的、有文件說明的獨立控制項,取代舊的 auth 區段。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
express, javascript, node.js
領域
authentication, backend
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
20/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。