Turn on CORS credentials for a separate Vue app
A separate Vue origin needs supports_credentials and an explicit origin. A same-origin Inertia app needs neither.
A separate Vue origin needs supports_credentials and an explicit origin. A same-origin Inertia app needs neither.
createToken can take an ability list. The ability middleware belongs on the API route, not on an Inertia page.
A first-party Vue SPA uses the session cookie. createToken is for a mobile client or another product.
auth on the Laravel route is what sends a guest to login. A v-if on the Vue page does not.
Fortify's login limiter is five attempts a minute. The Vue page shows the message on the username field.
Fortify's username config key is the input name. The Vue login form has to post that same name.
password.confirm sends the user to Fortify's confirm screen. The Vue form posts the current password once.
Fortify already exposes the forgot-password and reset-password URLs. The Vue form posts those fields and no others.
The Vue starter kit already verifies email. The user model must implement MustVerifyEmail, and the resend form posts to Fortify.
Leave SESSION_DOMAIN empty on one host. Set the parent domain only when Vue and Laravel are real subdomains.
A 419 after deploy is a CSRF cookie that the browser did not send. The app key, the domain, and HTTPS are the usual causes.
Pass query on the generated Wayfinder function. Do not glue a question mark onto the URL by hand.
Newsletter
One short email with new guides, release notes worth reading and hand-picked community links. No spam, unsubscribe any time.