Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I'm currently using the latest dev branch of ldap_integration and its associated modules in conjunction with the latest dev branch of the CAS module, and have noticed that upon logging in via CAS, the user's role is removed, but only so long as the LDAP database is not available.
I have tried disabling CAS completely and was able to reproduce the problem simply by logging in to Drupal. Additionally, I procured similar results using both LDAP and Drupal as the user repository.
Comments
Comment #1
johnbarclay commentedThe workflow of ldapgroups is to remove all the roles then reassign them. So if ldap server isn't available it will remove the roles. This is by design.
Are you proposing it leave the roles alone if it cannot connect to the ldap server?
Does CAS and ldap groups work toghether? My understanding was that ldap groups did not work without ldap auth.
Comment #2
cgmonroe commentedThe latest -dev version contains some extra checks before roles are changed. One of these is to verify that an LDAP error did not occur. If an error occurs getting groups (e.g. can't contact ldap server), nothing is changed.
For details see: #1475272: 6.x-1.0 Release Candidate 1 Status