Closed Benehiko closed 1 year ago
We would love to see this fixed as it's hurting our signup-flow!
To add some more details to this issue. We are seeing a similar problem, but at a different part of the flow.
When a new user access our site e.g. www.site.com
, and they are not authenticated, they go to the login screen, with a return_to=www.site.com
query parameter. We currently have two paths from this point.
If that user signs in, they are then returned to www.site.com
.
If that user does not have an account, and registers, they are sent to the registration
flow, which is requested with .../registration/browser?return_to=www.site.com
. The return_to
persists here.
But once they have registered, they are then sent to the verification
flow. But the return_to
is not included in this flow. It is being dropped somewhere. So after verification, our user is instead routed to the ory welcome page.
If this is not in the scope of this issue, then I am happy to make a new one.
I'll start investigating this today
Preflight checklist
Ory Network Project
No response
Describe the bug
When performing an OAuth2 flow the user might not have an existing account. This would lead to the user switching to the registration flow. When including the
login_challenge
in the request to create a registration flow the response correctly shows that the flow is part of an OAuth2 flow.After completing the OAuth2 flow using a
password
method, the response will include acontinue_with
to continue to the verification flow, as shown below:Following the verification flow will then result in a redirect to the default
/ui/welcome
page.Interestingly with the
one-time code
method, the OAuth flow continues as normal to the/consent
route.Reproducing the bug
continue_with
object. 8 . *optional - in case the UI shows the verification UI, perform it and you will be redirected to/ui/welcome
Relevant log output
No response
Relevant configuration
No response
Version
latest
On which operating system are you observing this issue?
Ory Network
In which environment are you deploying?
Ory Network
Additional Context
I used Ory Elements react-spa to test this out.