Use Authorizable trait in LdapUser to facilitate use with authorizati…

…on policies [refs #53]

Motivation and context

https://github.com/jotaelesalinas/laravel-adminless-ldap-auth/issues/53

How has this been tested?

Tested with a simple policy for an eloquent model, example function:

    /**
     * Determine whether the user can view the model.
     *
     * @param  \JotaEleSalinas\AdminlessLdap\LdapUser  $
     * @param  \App\Models\Candidate  $candidate
     * @return mixed
     */
    public function view(LdapUser $user, Candidate $candidate)
    {
        return $user->username == $candidate->uname;
    }

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

[x] I have read the CONTRIBUTING document.
[x] My pull request addresses exactly one patch/feature.
[x] I have created a branch for this patch/feature.
[x] Each individual commit in the pull request is meaningful.
[ ] I have added tests to cover my changes.
[ ] If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

jotaelesalinas / laravel-adminless-ldap-auth