Ldap auth for existing db user

[delta1186]

So I'm sure I'm missing something since I've been at this all day. I typically create new users in the database prior to their AD account being created. We also support non-AD users too. Currently using jetstream with laravel 8. When I attempt to login LdapRecord is finding the AD user. However it is not finding the associated DB user in order sync the domain and guid fields for the first time. Because of this it is trying to import the ldap user as a new DB user which fails because of some other unrelated reasons (missing required fields).

I tested this on my old implementation of Adldaps and if I deleted the guid field in the DB it would just get added back on next login.

I'm not sure what I'm missing with this implementation. I did switch to email for auth instead of username, but would not think that would make a difference.

I hope that makes sense.

[stevebauman]

Hi @delta1186,

Have you set up the sync existing configuration option? This is required so LdapRecord knows how to locate existing users in the database without a pre-synchronized GUID.

Let me know if you have issues or any other questions 👍

[delta1186]

@stevebauman yeah it is there and I think it is setup correctly.

'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\Models\Employee::class,
        ],

        'ldap' => [
            'driver' => 'ldap',
            'sync_existing' => [
                'email' => 'mail',
            ],
            'model' => LdapRecord\Models\ActiveDirectory\User::class,
            'database' => [
                'model' => App\Models\Employee::class,
                'sync_passwords' => true,
                'sync_attributes' => [
                    'first_name' => 'givenname',
                    'last_name'  => 'sn',
                    'email'      => 'mail',
                    'office'     => 'telephonenumber',
                    'mobile'     => 'mobile',
                    'title'      => 'description',
                ],
            ],
        ],
    ],

[delta1186]

[stevebauman]

Thanks for the quick response @delta1186.

The sync_existing array is not properly located inside of the database key. Nest the sync_existing array in the database key, and you should be all set:

// ...

'database' => [
    'model' => App\Models\Employee::class,
    'sync_passwords' => true,
    'sync_existing' => [
        'email' => 'mail',
    ],
    'sync_attributes' => [
        'first_name' => 'givenname',
        'last_name'  => 'sn',
        'email'      => 'mail',
        'office'     => 'telephonenumber',
        'mobile'     => 'mobile',
        'title'      => 'description',
    ],
],

[delta1186]

@stevebauman you are the man! That appears to have done the trick.

Dang and I just looked at the docs again and sync_existing being located under database was staring me right the face. haha.

While I have you where does the domain column get derived from? If my ldap url was say: ldap.example.com would the domain be "example"? For the record I just updated it ended up being "default"

[delta1186]

Nevermind, I see it is using the ldap config connection name here. Thanks again!

[stevebauman]

Happy to help @delta1186! ❤️