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 摘要。