Get AD user after login

[lucraraujo]

I need to filter information on the controller based on the OU of the user logged in via AD and I cannot find a way to access such information.
I'm using Database Authentication and the object returned to me is my from my User class.
My User class is this one:

<?php

declare(strict_types=1);

namespace App\Models;

use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Notifications\Notifiable;
use LdapRecord\Laravel\Auth\AuthenticatesWithLdap;
use LdapRecord\Laravel\Auth\LdapAuthenticatable;
use Spatie\Permission\Traits\HasRoles;

class User extends Authenticatable implements LdapAuthenticatable
{
    use AuthenticatesWithLdap;
    use HasRoles;
    use Notifiable;

    protected string $guard_name = 'web';
}

My AuthServiceProvider:

<?php

declare(strict_types=1);

namespace App\Providers;

use Illuminate\Foundation\Support\Providers\AuthServiceProvider as ServiceProvider;
use Illuminate\Support\Facades\Auth;
use Laravel\Fortify\Fortify;

class AuthServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        $this->registerPolicies();
        Fortify::authenticateUsing(static function ($request) {
            Auth::attempt([
                'sAMAccountName' => $request->username,
                'password' => $request->password,
            ]);

            return Auth::user();
        });
    }
}

[stevebauman]

Hi @lucraraujo,

Can you clarify what you mean by "filter information on the controller"?

Do you mean restrict access by redirecting the user with middleware? Or limiting what users can see inside of a blade view? Etc.

Give me an example of what you'd like to achieve, and I can help you get there 👍

[lucraraujo]

Hi @stevebauman !
The company I work for is spread across multiple cities and each user is organized inside the city "folder" (OU) and the data such user can see depends on the location. The problem I'm having is that I cannot get the AD information from the controller when I get the user via Laravel Auth::user() facade.
Since I use a auditing library (owen-it/laravel-auditing) I had to use Database based auth, otherwise I would result do databaseless authentication.
I don't know if I could make myself clear about my problem.

[stevebauman]

Ok I understand. Database auth is totally fine. Either option will work the same.

I would first add the following trait onto your User.php model:

// ...
use LdapRecord\Laravel\Auth\HasLdapUser;

class User extends Authenticatable implements LdapAuthenticatable
{
    use HasLdapUser;

    // ...
}

This provides a Laravel Model Accessor named ldap. This will return you the users LdapRecord model instance, allowing you to retrieve their OU:

$user = Auth::user();

// LdapRecord\Models\ActiveDirectory\User
$user->ldap;

// "ou=users,dc=local,dc=com"
$user->ldap->getParentDn();

With being able to access your authenticated user's LdapRecord model via the ldap accessor property, you can retrieve any attribute that you need for filtering out data on the frontend.

Let me know if that answers your question 👍

[stevebauman]

Cool! Sounds good -- definitely a viable option as well. I'm glad you were able to resolve this.

[lucraraujo]

It worked! Thank you so much!

[stevebauman]

Excellent! Happy to help @lucraraujo 🎉