-
Notifications
You must be signed in to change notification settings - Fork 970
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: registration should accept hydra login #3592
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this! The approach is sensible, I just think we should look for prompt=login
instead of skip
.
78cd2d3
to
71f3634
Compare
Codecov Report
@@ Coverage Diff @@
## master #3592 +/- ##
==========================================
- Coverage 78.24% 78.22% -0.03%
==========================================
Files 341 341
Lines 23098 23129 +31
==========================================
+ Hits 18073 18092 +19
- Misses 3674 3683 +9
- Partials 1351 1354 +3
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Related issue(s)
https://github.com/ory-corp/cloud/issues/5493
Using
propt=registration
on an OAuth2 Hydra login flow, the request is routed to the Kratos registration handler. This handler immediately redirects to the logout flow when there is an already existing session, which fails and ends up at the base/welcome
page on the Account Experience (AX).This PR adds the functionality of accepting the login request in the registration handler if the user has a session and if the hydra
skip=true
is in the login request.When the
skip=false
is set, the request is redirected to the login flow with the login_challenge, which will complete the flow normally.Checklist
introduces a new feature.
contributing code guidelines.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got the approval (please contact
[email protected]) from the maintainers to push
the changes.
works.
Further Comments