I've written the initial pass of Fortify documentation which documents all of the backend features that were available via the laravel/ui package:
Fortify is a headless authentication backend for Laravel. Think of it as the backend authentication logic that used to be in laravel/ui but without any specific frontend attached to it. You bring your own frontend. However, a great example of how to implement the templates is not only documented but is available for review with the Blade based authentication views in Jetstream: [https://github.com/laravel/jetstream/tree/1.x/stubs/resources/views/auth](https://github.com/laravel/jetstream/tree/1.x/stubs/resources/views/auth)
In summary, you can use Fortify as a backend for any frontend stack you want. Someone could even publish frontends as a package (like Jetstream!) on any stack you want, such as Bootstrap.css, etc.
19 thoughts on “Laravel Fortify Has Been Documented”
This is great and exactly what many folks want. You rock!
Amazing, great work on Fortify and Jetstream. Thank you.
/u/TaylorCodes thank you for listening to all of the community not just the many. This really helps.
Thanks. I was wondering about this recently after having jumped back into Laravel since like version 5.x. It felt weird to me that the auth stuff was tied around UI stuff. Was trying to find a way to add the backend routes without any of the frontend bits, but sadly there didn’t seem to be an option for it on the artisan command. Ended up having to just manually add the bits in.
Is it recommended for API auth too? Actually, I don’t know any packages that has built-in controllers for API Auth.
Anyone planning to use it in an API?
Still a bit confused, but would fortify work with passport then?
Thank you very much! I was really looking for this since I first heard of Fortify. I really appreciate the `features` approach!
May I ask what is that pipeline pattern with actions? Is it meant for passing a request through multiple functions instead of one controller action?
I’m going to have to implement SSO in the near future. Would Fortify play well with a custom auth on sign in for that, or should I look to other solutions?
Just started a new project and am about to work on the Auth part in a few weeks. Post saved and will offer feedback once I’ve checked it out
Does this use Sanctum behind the scenes?
Me: taylor, taylor, taylor. We love you taylor. Make love to me taylor.
Can someone tldr; it for me- does this replace passport, or is it refactored from passport as a sub-component or convenience layer on top of passport?
Probably unrelated, but can I replace `Fortify::loginView()` to return `Inertia::render()` instead of `view()`?
I’m getting an error as “Unable to locate publishable resources.” while trying to publish the ServiceProvider. Is it only me or anyone else is also facing this issue??
this is really nice, thanks 🙂
Hi I am loving Laravel 8! I was wondering if its possible to create 2fa and session management like Jetstream with fortify standalone. Looking through the code it looks like we can. If possible will there be documentation on it in the future?
EDIT: It is possible. After giving it a shot I am in love with this. I can quickly bootstrap auth with 2fa and use any front end like Angular! Thanks for the hard work truly a great product! Anyone wanting to implement Fortify just have a look at Jetstream’s implementation.