You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've come accross a bug where I am not redirected to my client on a successful authentification. The flow work perfectly until the point where the server should redirect me to my client. I first it was flagged as a CORS error, then I solved the supposed error bug I was still not redirected.
I've disabled Turbo and it worked perfectly, any idea why?
Something to note is that, when I try to connect when turbo was on, I was redirected to my login page, but I was connected. so if I manually try to access my client or any other page that is user restricted, I had no issue.
The text was updated successfully, but these errors were encountered:
Is Turbo enabled in the server, the client or both? In an application that uses turbo, I recommend adding the data-turbo="false" attribute to any anchor or form that might ultimately redirect to another domain to avoid CORS errors.
As an alternative, you can use the workaroud I wrote sometime ago, that is referenced in my comment to the related Turbo issue hotwired/turbo#203.
I've come accross a bug where I am not redirected to my client on a successful authentification. The flow work perfectly until the point where the server should redirect me to my client. I first it was flagged as a CORS error, then I solved the supposed error bug I was still not redirected.
I've disabled Turbo and it worked perfectly, any idea why?
Something to note is that, when I try to connect when turbo was on, I was redirected to my login page, but I was connected. so if I manually try to access my client or any other page that is user restricted, I had no issue.
The text was updated successfully, but these errors were encountered: