Removed 3.0.0 restriction for the Ldap component in the Security component #18201
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This ticket removes the restriction on version 3.0 of the Ldap component, as the component is now both backward and forward-compatible.
This PR is being made against the
3.0
branch and not in the2.8
branch as it seems that all other dependencies rely on~2.8|~3.0.0
for the2.8
branch.There will be a conflict with the
master
branch. The versions to use on themaster
branch is~3.1
for bothcomposer.json
files, as the authentication provider and the user provider rely on the new interface, and theLdapInterface::query()
method, instead ofLdapClientInterface::search()
, which is deprecated.