Redirect URL for registration flow not respected when user is already registered

[mooijtech]

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

If I delete my cookies and run the registration flow for OIDC again I get the following:

Received successful OpenID Connect callback but user is already registered. Re-initializing login flow now.
Running ExecuteLoginPostHook.
Identity authenticated successfully and was issued an Ory Kratos Session Cookie.

But it is not respecting my returnTo URL (specified in code).

The returnTo URL does work if the user is not already registered.

Reproducing the bug

1. Configure a OIDC provider (I used Microsoft)
2. Perform register flow
3. Delete cookies
4. Perform register flow again
5. Return URL is not respected (as specified in the initializeSelfServiceRegistrationFlowForBrowsers).

Relevant log output

No response

Relevant configuration

ory.initializeSelfServiceRegistrationFlowForBrowsers("/integrations/" + integration).then(({data}) => {
                setFlow(data)
            }).catch((error) => {
                if (error.response?.data.error?.id === "session_already_available") {
                    handleAuthenticated();
                } else {
                    return handleFlowError(router, "integrations/" + integration, setFlow)
                }
            })

router.push(`/integrations/${integration}?flow=${flow?.id}`, undefined, {shallow: true}).then(() =>
            ory.submitSelfServiceRegistrationFlow(String(flow?.id), {
                csrf_token: flow?.ui?.nodes?.[0]?.attributes?.value,
                method: "oidc",
                provider: integration,
            }).catch(
                handleFlowError(router, "integrations/" + integration, setFlow)
            ).catch((error) => {
                // If the previous handler did not catch the error it's most likely a form validation error.
                if (error.response?.status === 400) {
                    setFlow(error.response?.data)
                    return
                }

                return Promise.reject(error)
            })
        )

Version

v0.9.0-alpha.3

On which operating system are you observing this issue?

Linux

In which environment are you deploying?

Binary

Additional Context

No response

[leecalcote]

I'm facing the same issue. Did you find a resolution or work-around for this, @mooijtech?

[mooijtech]

@leecalcote Unfortunately not.
Seems to reference #2805 which is still in the latest release.

[supercairos]

I'm working on a fix for this issue. It should be an easy fix

[supercairos]

This can be closed as it's been merged into master

[mooijtech]

@supercairos Thank you, appreciate it.