Redirect problem after login to refresh privileged session
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker-compose
调研方向
该 issue 未指明任何文件或测试；首先使用文档所述的 return_to URL 和 GetSelfServiceSettingsFlow 调用，从自定义设置页面复现特权会话流程。跟踪登录重定向，并验证返回设置页面后，特权操作能够完成，不会出现 GET 方法错误，也不要求用户重复执行该操作。
由索引模型根据 Issue 内容生成。
描述
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Cloud project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe the bug
When the user needs to login to refresh a privileged session (e.g. from the settings page), it is redirected from the current page to the login page with the following return_to url:
http://ory.domain.com/self-service/settings?flow=FLOW_ID
After a successful login, the login page should redirect the user to the address at return_to (above).
Redirecting the user there ends up in the settings page. Calling GetSelfServiceSettingsFlow at that stage provides a flow with the error below and the user needs to repeat the last action:
Unable to decode body because HTTP Request Method was "GET" but only [POST PUT PATCH] are supported.
We assume this is a bug and that at this stage we should have a settings flow updated after completing the operation the user tried to perform. We also tried to compare the settings flow from the first call and after the login, but they are pretty much the same, so no clue on what should be done differently.
Please advise.
Reproducing the bug
- Configure your Ory Session privileged timeout to a small interval (e.g. 30s)
- Go your custom kratos ui settings page
- Execute a privileged action (e.g. reveal backup recovery codes)
- Wait for redirect to login
- Enter the correct credentials
- Wait fo redirect back to settings
- The error message is shown and the privileged action is not executed
Relevant log output
No response
Relevant configuration
No response
Version
0.0.1-alpha.169
On which operating system are you observing this issue?
Windows
In which environment are you deploying?
Docker Compose
Additional Context
No response
- 主要语言
- Shell
- 星标
- 96
- 派生
- 8
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ory/network 的其他 Issue
-
bug
难度 4/5 3-5 天 新手友好度 38/100
-
Updating native registration flow with OIDC ID token for existing identity returns breaking response未关闭bug
难度 4/5 3-5 天 新手友好度 35/100
-
feat
难度 5/5 一周以上 新手友好度 25/100
-
bug
难度 4/5 3-5 天 新手友好度 30/100
-
feat
难度 5/5 一周以上 新手友好度 35/100
相似的 Issue
-
bot-found bug priority: P3
难度 2/5 1-3 小时 新手友好度 84/100
madenvel/KalinkaPlayer#179 ·
-
documentation
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 86/100
jbaruch/coding-policy#621 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
mattpocock/skills#1134 ·
-
area:build bug P3
难度 1/5 1 小时以内 新手友好度 92/100
uttrflow/uttrflow-swift#2506 ·
维护者通常 1 天内回复