no need to get the tokens in the main js code (and it defeats the purpose)
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript
调研方向
Start with the README's OAuth 2.0 guidance and the main JavaScript/service-worker boundary described in the issue. Compare the proposed service-worker token interception, authorization-code exchange, and silent refresh flow with the current behavior. Done means token acquisition and storage remain in the service worker without returning tokens to the main application, with renewal and discarded-worker handling addressed.
由索引模型根据 Issue 内容生成。
描述
Readme:
In an OAuth 2.0 environment, this can present a challenge - the typical means of obtaining access tokens is via browser redirection (user interaction is sometimes required). For this reason, only the specific concern of making token-bearing requests must be handled within the service worker. All other concerns (such as actually obtaining tokens from the authorization server) must be handled in the main execution context.
The service worker can perfectly intercept the redirect with authorization code, exchange it for tokens, and keep it securely without giving them back to the main js application. Token renewal (or when the sw gets discarded) can still be handled by a "silent refresh" flow, for example. You don't even need the SW to communicate with the app anymore with that solution (well, you do need a kind of hearth beat to keep the SW alive).
Some POC implementation here:
https://github.com/Valuya/servicewauther
Some other want I stumbled upon today:
https://infinum.com/blog/secure-token-storage-oauth2/
https://github.com/infinum/auth-worker
And maybe this:
https://about.grabyo.com/service-workers-jwt-tokens/
- 主要语言
- JavaScript
- 星标
- 52
- 派生
- 16
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ForgeRock/appAuthHelper 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 55/100
ForgeRock/appAuthHelper#68 · 2 个 reaction ·
-
Cannot read properties of undefined (reading 'clientId'): appAuthHelperFetchTokensBundle.js:46:635未关闭
难度 3/5 1-2 天 新手友好度 38/100
ForgeRock/appAuthHelper#67 ·
-
难度 5/5 一周以上 新手友好度 25/100
ForgeRock/appAuthHelper#62 ·
-
难度 4/5 3-5 天 新手友好度 35/100
ForgeRock/appAuthHelper#60 ·
-
难度 3/5 1-2 天 新手友好度 25/100
ForgeRock/appAuthHelper#59 ·
查看 ForgeRock/appAuthHelper 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 76/100
521xueweihan/HelloGitHub#3939 ·
-
难度 1/5 1 小时以内 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 79/100
aemsites/author-kit#19 ·
-
needs-website-changes
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复