Accept a user identity forwarded by a credentialed server

未关闭
  • 哪里不对？
#4,238 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

这个 Issue 还没有评估数据。

描述

PolicyEngine's web servers will call the Public API with their own server credential in Authorization (#4236). When such a server acts for a person, the signed-in user routes (/v2/me*, /v2/user-*) need to know who that person is, but Authorization is already taken by the server's token.

Done when:

  • a credentialed server can forward a signed-in user's Auth0 token in PolicyEngine-User-Authorization: Bearer <token>, or a signed-out browser's PolicyEngine-Unauthenticated-User header;
  • the user routes treat that user exactly as they treat a direct request with the same credential today, including POST /v2/me/upgrade;
  • until enforcement, a user's token sent directly in Authorization keeps working, and PolicyEngine-User-Authorization is ignored on any request without a server credential.
主要语言
Python
星标
18
派生
33
平均合并
2 天 14 小时
30 天内合并 PR
116

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

PolicyEngine/policyengine-api 的其他 Issue

查看 PolicyEngine/policyengine-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。