Closed ashkellerman closed 7 months ago
Everywhere online states to remove the html tag containing the csrf_token()
from the main layouts but I have not noticed any difference by doing so.
@ashbakernz There's always a few places to check with Sanctum.
Did you update your Session domain .env to .test
. That will allow the secure cookie to be submitted with SESSION_DOMAIN=.test
.
I'll check out the register page as well
Hi all. I confirm this as well. Any form from the registration page on, returns a 419. Cloned just a few mins ago
Closing this issue due to inactivity.
FYI, Financial Freedom is getting a major overhaul. See our README file for the latest details: https://github.com/serversideup/financial-freedom#readme
Issue description
Get a 419 error when attempting to login/register. This may have something to do with sanctum. I tried updating my .env (SANCTUM_STATEFUL_DOMAINS) but no luck! Maybe the .env.example needs updating? I'm unsure.
It's a 100% something to do with the csrf token as if I disable (VerifyCsrfToken) middleware in kernal it kinda fixes the issue but then causes more issue.
Environment
valet
and mysql hosted locally. (Unsure how to get docker running 🤷 )Steps to reproduce the issue
What is expected?
API should return results.
Link to where issue can be reproduced
Fresh install and attempting to register/login.
Additional details / screenshots