rummanrc

Hi, did you manage to solve this? I'm also facing a similar issue right now.

It seems like for every Auth::attempt or Auth::guard()->attempt() the AdldapAuthServiceProvider class is being used, regardless of the guard. I don't know why it's passing through though, without credentials.

No matter which guard I use, the Adldap2's DatabaseUserProvider is getting used. I think that might be causing this conflict? If yes, can I bypass this so that the DatabaseUserProvider...

So I had to override the Adldap2-laravel's DatabaseUserProvider class and put a condition on the retrieveById function. I added custom claims in the tokens of my models, and checked for...