- πΊπΈUnited States AaronBauman Philadelphia
Similar issue here, and it's happening on the latest release.
If I have an LDAP user with an email that already exists in Drupal, what's the suggested workaround here? - π©πͺGermany Rudi Teschner
In my opinion the only plausible solution would be to skip the conflicting user, add the proper watchdog message and continue syncing the rest of the users.
- Status changed to Needs review
over 1 year ago 2:50pm 14 March 2023 - πΊπΈUnited States AaronBauman Philadelphia
Here's the patch that's working for me.
Setting priority back to Normal, but I could see a case that throwing a fatal during cron run is at least Major. - @aaronbauman opened merge request.
- πΊπΈUnited States AaronBauman Philadelphia
Maybe I can get a MR working instead of a patch...
- First commit to issue fork.
-
sergiogsanchez β
committed 0d2858bc on 8.x-4.x authored by
AaronBauman β
Issue #3192905 by AaronBauman: More graceful handling in...
-
sergiogsanchez β
committed 0d2858bc on 8.x-4.x authored by
AaronBauman β
- Assigned to sergiogsanchez
- Status changed to RTBC
over 1 year ago 4:38am 17 March 2023 - π¨π΄Colombia sergiogsanchez
I have tested the patch on Drupal 9.5.5, and it's working as expected skipping the user with errors or not externalauth results
- Status changed to Fixed
over 1 year ago 2:46pm 20 March 2023 Automatically closed - issue fixed for 2 weeks with no activity.