LDAP Start TLS causes blank pages to be returned upon login
arran4 - July 1, 2009 - 07:46
| Project: | LDAP integration |
| Version: | 6.x-1.0-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
LDAP Start TLS causes blank pages to be returned upon login. When ever I enable the option, users are unable to login and greet a blank page.
#1
Could you inspect web server's log for a concrete error which is causing the white screen?
#2
This happens with the beta1 as well.
I do not expect the ldap server I am using to have start-tls support enabled, so I suspect this will happen when start-tls is not supported on the ldap-server end and authentication fails.
Heres my log messages:
ldap_start_tls() [<a href='function.ldap-start-tls'>function.ldap-start-tls</a>]: Unable to start TLS: Connect error in /var/www/html/sites/all/modules/ldap_integration/includes/LDAPInterface.inc on line 154
Could not start TLS. (Error -11: Connect error).
ldap_errno(): supplied argument is not a valid ldap link resource in /var/www/html/sites/all/modules/ldap_integration/includes/LDAPInterface.inc on line 167
ldap_error(): supplied argument is not a valid ldap link resource in /var/www/html/sites/all/modules/ldap_integration/includes/LDAPInterface.inc on line 167
LDAP Bind failure for user . Error
Those messages are from a single failed login with start-tls enabled for an ldap-server that probably does not have start-tls enabled.
#3
Of course LDAP server should be configured to use TLS if you have enabled it on drupal end.
#4
The problem is that, the messages are not logged and the user gets a blank page.
In other words, the failure is not graceful.
They should be returned to the page they were logging in from and presented with an error message instead of effectively sending the user to /dev/null