There are various places where the server configuration status (enabled/disabled) is not checked before performing LDAP server requests. Adding checks for server status would allow for a more flexible system that can be toggled on and off as needed. For instance: developer environment - server config disabled, production environment - server config enabled.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

recrit’s picture

the patch attached adds server config status checks in the majority of places where server requests would be made. This most likely does not capture all of them.

recrit’s picture

Status: Active » Needs review
johnbarclay’s picture

Title: Improve checking server status before performing LDAP requests » LDAP Server: Improve checking server status before performing LDAP requests

Thanks. We should just leave this issue open until there is more coverage. I'll commit these as they come along. A search for calls to the get server functions should locate them all.

recrit’s picture

grahl’s picture

Status: Needs review » Needs work
grahl’s picture

Status: Needs work » Needs review

The last submitted patch, 1: ldap-check-server-status-2043539-1.patch, failed testing.

The last submitted patch, 1: ldap-check-server-status-2043539-1.patch, failed testing.

The last submitted patch, 1: ldap-check-server-status-2043539-1.patch, failed testing.

grahl’s picture

Can someone confirm, that this works with our regressions? Ideally in multiple environments?

grahl’s picture

Status: Needs review » Closed (won't fix)
Related issues: +#2459589: LDAP Authentication: provide an enabled variable (TRUE / FALSE)

We don't need this in 8 due to the configuration system in general for multiple environments and workarounds for 7 have been provided in the related issue. Therefore I'm closing this issue.