At least with ldap_sso for full domain active and possibly more. Needs retesting and analysis. Potentially an issue with masquerade itself and not LDAP.

Comments

grahl created an issue. See original summary.

grahl’s picture

grahl
he/him
Location Zürich
CreditAttribution: grahl as a volunteer commented
Project: Lightweight Directory Access Protocol » LDAP Single Sign On
Version: 8.x-3.x-dev » 7.x-2.x-dev
grahl’s picture

grahl
he/him
Location Zürich
CreditAttribution: grahl as a volunteer commented
Version: 7.x-2.x-dev » 8.x-1.x-dev
rgristroph’s picture

rgristroph CreditAttribution: rgristroph at Acquia commented
Version: 8.x-1.x-dev » 8.x-1.0-beta7

I am seeing this with the beta7 version of ldap_sso and the beta2 version of masquerade.

rgristroph’s picture

rgristroph CreditAttribution: rgristroph at Acquia commented

I have a work-around: if you don't set the ldap_sso option to redirect on logout, then it works. Note that the masquerade module calls the user_logout() hook, which I think is where the conflict is coming from.

Note this issue over on the masquerade module: https://www.drupal.org/project/masquerade/issues/2896370

WorldFallz’s picture

WorldFallz CreditAttribution: WorldFallz commented

FYI same issue with devel module's switch user functionality.

Disabling redirect on logout also enables it to work again.

  • grahl committed 68ee15c on 8.x-4.x 
    Issue #2889863: LDAP conflicts with Masquerade 2.0
grahl’s picture

grahl
he/him
Location Zürich
CreditAttribution: grahl as a volunteer commented
Status: Active » Postponed

Thanks for the feedback and documenting this workaround. I've added that as conflict in the field description so most users should see it.

If someone has another idea how to detect those cases reliably from the expected case, please provide feedback or a patch, setting to postponed for now.