You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure it's an issue with devise_ldap_authenticatable as such but I thought it would be worth sharing here in case anyone else runs in to this problem:
After upgrading to 0.4.9 I started getting the following exception when authenticating against LDAP:
Net::BER::BerError in Devise::SessionsController#create
Unsupported object type: id=139
with the following in the Terminal window:
Started POST "/d/users/sign_in" for 127.0.0.1 at 2011-07-11 11:58:45 +0100 Processing by ?>Devise::SessionsController#create as HTML Parameters: {"utf8"=>"✓", >"authenticity_token"=>"T+ttL/6YPK1A/HE4XRukI7SKHDTVr553/hOD+5UyYUk=", "user"=>{"username"=>"admin", >"password"=>"[FILTERED]", "remember_me"=>"0"}, "commit"=>"Sign in"} SQL (0.4ms) SELECT name FROM sqlite_master >WHERE type = 'table' AND NOT name = 'sqlite_sequence'
User Load (1.3ms) SELECT "users".* FROM "users" WHERE "users"."username" = 'admin' LIMIT 1 LDAP: LDAP search: >uid=admin Completed 500 Internal Server Error in 659ms
After a bit of digging the problem seems to be related to net-ldap 0.2.2, so I've created a fork to restore the old 0.1.1 dependency. I'm sure this fork will break at some point in the future (but it seems OK for my basic usage at the moment).
If there's anything I can do to help come up with a more permanent fix then I'm happy to help.
-Ash
The text was updated successfully, but these errors were encountered:
Hi,
I'm not sure it's an issue with devise_ldap_authenticatable as such but I thought it would be worth sharing here in case anyone else runs in to this problem:
After upgrading to 0.4.9 I started getting the following exception when authenticating against LDAP:
with the following in the Terminal window:
After a bit of digging the problem seems to be related to net-ldap 0.2.2, so I've created a fork to restore the old 0.1.1 dependency. I'm sure this fork will break at some point in the future (but it seems OK for my basic usage at the moment).
If there's anything I can do to help come up with a more permanent fix then I'm happy to help.
-Ash
The text was updated successfully, but these errors were encountered: