Steve Bauman

Hi @saabarukyatto, that's strange. The `UserResolver::getAppAuthProvider()` method is supposed to return your default guard provider, but it seems to be returning `null`... Can you try calling `dd(Auth::guard()->getProvider())` at the top...

Strange... Something isn't configured correctly, because it should return your default guards provider. Can you try flushing your config cache using `php artisan config:clear`? Also, this seems to be an...

Hi @rnrstar, Does the user that you created have a password set? You must set the users password before enabling them, otherwise you will receive this error from ActiveDirectory.

Hi @SaeidJorablo, When you created this new user in active directory, did you remove the default “User must change password on next logon” flag that is set on new users?...

Hi @briancardonas, what database are you using? If you're using Postgre or other case-sensitive databases, you need to call `strtolower()` on usernames prior to authenticating users.

Hey everyone, I promise I'm not ignoring you! Just really swamped with internal projects at the moment. A new user will only be created if the initial lookup of the...

Hi @murrant, Mind sending a PR so I know what you mean for implementation?

Hi everyone -- I'd honestly suggest moving to [LdapRecord-Laravel](https://ldaprecord.com/docs/laravel/auth/laravel-jetstream/#fallback-auth) for this feature -- as it provides the exact functionality you are looking for 👍 Adldap2-Laravel is in a feature freeze,...

Hi @tcagkansokmen, LdapRecord supports this feature out of the box. I’d recommend moving to it: https://ldaprecord.com/docs/laravel/v2/auth/database/configuration/#sync-existing-records

Hi @Roemerb, The `Resolver` will always return Adldap models, not your `App\User` instance. It's job is to locate the user in your ActiveDirectory. Default `Entry` models are returned when Adldap2...