Bump adldap2/adldap2 from 10.0.6 to 10.0.8

[dependabot-preview]

Bumps adldap2/adldap2 from 10.0.6 to 10.0.8.

Release notes

Sourced from adldap2/adldap2's releases.

v10.0.8

Added

• clearFilters and addFilter methods to Query\Builder - 77e85c9 - #654

Fixed

• Clear filters when locating group members by alternate attribute (ex. uid) - 140eae3 - #654
• newParentDn parameter for Model::rename() is now defaulted to null for easier renames - f78608e
• Query\Builder::get() will now use a default (objectclass=*) filter when no filters are present - 07fcbb3 - Searching in OU returns empty items array Adldap2/Adldap2-Laravel#707

v10.0.7

Added

• User::getBadPasswordTimestamp & User::getBadPasswordDate methods - 8ce5f62
• User::getLockoutTimestamp & User::getLockoutDate methods - 1b1ffee

Fixed

• Calling collection methods (sortBy, pluck, map, filter etc.) on query results will now work properly and use the models first available attribute - f1c75e3 - #616
• Calling $user->getProxyAddresses() will now always return an array - 26f3bc4
• Only sort query results if specified - f1c75e3

Commits

• 2865b4d Use expectException method instead of depreciated annotations
• abc90db Added more tests
• 2bd5489 Ensure the proper binding keys are given when adding filters
• 140eae3 Clear filters before locating each group member
• 6853e2f Use consistent spacing for logical operators
• 77e85c9 Added addFilter and clearFilters methods
• a2e357b Revert detecting SELinux
• 71841a8 Modify exception message in BindException constructor for SELinux
• 10f0ab0 Added extra exception detail when using SELinux
• 017ce9f Added ability to determine if SELinux is being used
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[prytoegrian]

Comment review ?

Comme toute PR dependabot, la review est plus qu'anecdotique, même si ça ne fait pas de mal de passer dessus. Le but est de s'assurer que dependabot a bien fait son travail et que les versions notées ne sont pas fluides.

Comment tester ?

Le mieux est de passer par le docker. Une fois le process d'installation suivi, tirez cette branche et faites make install, l'application mettra à jour la dépendance.
Essentiellement, le test consiste à vérifier que la connexion avec le serveur LDAP. Pour ce faire, rendez-vous sur l'appli web en RH pour activer la connexion par LDAP dans les paramètres. Une fois fait, vérifiez dans le docker que les utilisateurs sont bien importés. Si tel n'est pas le cas, exécutez le script d'import. Il vous faudra installer l'addon RESTED, dispo sur Chrome et Firefox.
Le cœur du test peut enfin commencer : remplissez les infos comme suit, ajouter les identifiants : hr / hrldap et tentez de vous connecter.
Si vous avez un token d'identification, le test est validé.

[dependabot-preview]

Superseded by #101.