Hi @dan.woda, thanks for the reply. I’m new to this and slightly drowning in some of the concepts and complexity so any help is very much appreciated!
I was originally using a Rule as part of the login flow setting
context.redirect to my Url and then returning the callback function with the
context as an argument. This worked well but my understanding is Actions are preferable to Rules going forward so I rewrote my Rule as an Action. I guess my Rule was also resulting in an incomplete login process.
For background, I’m trying to implement Shopify’s Multipass login and as per the docs, I need to redirect users to
https://SHOPIFY_DOMAIN/account/login/TOKEN (where TOKEN is what I’m successfully generating in my Action) after Auth0 authentication has taken place.
Weirdly the result of both the Rule and the Action achieve what I’m hoping for in that I’m logged into my application (app A), the redirect takes place and the authentication session is shared across both app A and another application, app B. Logout also works as expected. My assumption is that despite this, the issue must be addressed as without returning to the
/continue endpoint, no further Actions in the Flow will run.
I also noticed the same technique I’m using is used for the downtime page example here, but I assume returning the user to
/continue is just omitted for brevity?
Thanks again for any help.