I have a login page which is receiving back from my server a token. It is being set correctly in cookie storage on the client, but the redirect does not trigger and the login page is reloaded.
I can get the redirect page to load by either:
(1) If I type the redirect url manually, then the page loads correctly (I can see that the token is being sent correctly - so the token has been saved).
(2) Typing the credentials in a second time on to the login page and submitting, then the redirect works correctly (in this case the server will send a new token).
What I have noticed from my server logs, is that after the first attempt to call the redirect, the server receives {{ cookies.access_token }}.
When typing in manually (or after the second submit), the server is receiving the token. I have attached screenshots.
The workflow is very simple (as attached).
As per @Lucas G suggestion I put prevent default at the start of the submit workflow, but that has not helped in this case.
Any pointers would be really appreciated.
.jpeg/public)