As far as I can see in the code it's only focused on one guard. In general, an extra guard is normally used for APIs or third party access. Not for a user and admin guard.
Also, note that Fortify is there to give you a quick start, it won't fit all cases.
Well actually if you want to use frontend users seperate from the backend users is it cleaner to create two tables with user credentials so one cant login to other and where you can authenticate between different guards
so does anyone know when fortify will ben multi guard authentication work?
It looks like fortify is set up for only a smaller type scenario. Allowing only one type of login and redirect at a time rather than a robust Enterprise type authentication system. The redirect part has been solved however.
There are a large insurance chains , such as Humana that has major login sections Physicians, patients, and government entities all separate of course.
Fortify does not seem to be geared up for such an Enterprise development.
Whereas with laravel UI the developer has much more freedom to program such a large Enterprise development scenario.