Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By tsandlin451 on
We're having a problem getting our openid server working properly with our Drupal server. I'm able to authenticate properly with Verisign, etc., but when I attempt to login with our openid server, I get:
"Sorry, that is not a valid OpenID. Please ensure you have spelled your ID correctly."
However, when we attempt to authenticate to other websites with that same openid server, we are not having any problems - authentication works perfectly. Indeed, it would appear from our openid server that Drupal is not even touching it. Further, there is nothing in the logs whatsoever - we get that error message on the screen, but the logs (and I have turned on logging to syslog) show nothing at all - on successful openid and regular logins, we get plenty of information in the log files.
Are we missing a step somewhere? Is there a more detailed logging available for Drupal core? I'm confused why openid logins to outside domains would work perfectly but the inside server fails without even touching the openid server.
Our config:
Drupal server:
SUSE 11.1
Acquia Drupal 1.2.21 (Drupal 6.15 core)
PHP 5, MySQL 5, Apache 2.2
Openid server:
Solaris 10
OpenID-ldap (to an AD env.)
Please note - we haven't installed any of the ldap modules on the Drupal server itself, since it is not meant to communicate with the ldap server - all of that is handled on the openid server side.
Any suggestions would be appreciated.
Comments
should add
I should add that our openid-ldap server is working to authenticate to other sites. The only one we seem to have a problem with is the Drupal server.