nodeSolidServer / nodeSolidServer/node-solid-server
`UserInfo` endpoint lookup never returns
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 1.8k
- 分支
- 308
- PR 合併指標
- 30 天內沒有已合併 PR
描述
As part of the OIDC login flow, during the backchannel exchange to get the access and id token (assuming you are in the auth code flow, but that's not relevant to the issue), one can perform a check against the UserInfo endpoint of the OIDC provider to check that the sub claim of the obtained ID token matches the one of the userinfo associated to the access token.
However, in the case of NSS, a lookup at https://inrupt.net/.well-known/openid-configuration shows that the userinfo endpoint exists, but a GET to https://inrupt.net/userinfo just hangs, and never get either a success or an error response. This prevents proper functioning of some OIDC libraries, and requires to be worked around. Should this be fixed in the NSS repo, or rather at the oidc-op level ?
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
重現 https://inrupt.net/userinfo 上掛起的 GET 請求,並將其與 https://inrupt.net/.well-known/openid-configuration 中公布的端點進行比較。追蹤確認 UserInfo 行為是由 NSS 還是 oidc-op 負責;完成的條件是該端點返回成功回應或錯誤回應,讓 OIDC 程式庫能夠完成驗證。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript
- 領域
- api, authentication
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 35/100