Issue with Custom Guard and Provider in Filament - "Route [login] not defined" Error

[jmendozaf]

In my application, I have set up a custom guard and provider (admin) in config/auth.php to handle authentication instead of the default web, primarily for Filament only. I thought this might be causing some conflicts with the lockscreen package, particularly with route definitions.

The specific error I am facing is: "Route [login] not defined." This error occurs when trying to lock my screen, and I suspect it is related to my custom admin guard and provider setup.

[MarJose123]

Can you check, if your default panel used the web guard if the plugin is working fine, and the same with the custom guard?

Can you share some error logs details for me to debug.

The error you encountered is more on middleware of laravel Authenticate.

The lockscreen are using session it means that the user is not currently login.

[jmendozaf]

The default panel with the web guard and the plugin works fine! Also, the default or custom panel with the custom guard functions properly. The user is logged in. I think that the issue lies with the middleware using the plugin. Besides the issue with the lock screen, everything works as expected. I'm attaching some screenshots.

[MarJose123]

I see, I got it.

This is an issue I think within the validation and the plugin is not using the defined guard for authentication.

I will fix this during my free time, you are welcome also to PR.