-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Crayfish-Commons dependency on symfony/security-core to allow 5.x #1903
Comments
I went looking but couldn't find a good listing of security-core API changes.... |
that ellipsis makes me think that you weren't successful |
Indeed, I wasn't. |
@seth-shaw-unlv can you give me more info on this one? what kind of environment are you running in? are you already on D9 in that env? |
This was a D8 install with ldap 3 updating to D9. Perhaps I should spin up a fresh D8 Islandora, enable ldap 3, and try upgrading to D9 w/ ldap 4. |
Seth was updating an existing Islandora 1.0 site and had composer complain about this conflict. Eli tried to test and he was not able to reproduce. Where exactly is the hitch with the update progress? |
From @jordandukart https://packagist.org/packages/grahl/ldap - Eli pulled islandora-dev and Seth pulled in tagged version. Seth will try to reproduce. |
Okay. I took an isle-dc and modified the So, can't reproduce. It must have been something weird I was doing with composer or my particular site. Closing as "can't reproduce". |
The Drupal ldap module major version 4.0, the only version with Drupal 9 support, conflicts with symfony/security-core < 5 resulting in a conflict with crayfish-commons which requires either 3.4 or 4.4. This means that those using LDAP for authentication are stuck on Drupal 8 until this is resolved.
I haven't yet checked what we need to do to make crayfish-commons work with symfony/security-core:^5, if anything.
Tagging @elizoller as the current crayfish-commons maintainer.
The text was updated successfully, but these errors were encountered: