Closed mem closed 12 years ago
What you did should work fine, but I have a feeling that it broke with the Devise 1.3 or 1.4 update. I confess, I haven't actually tested this use case in awhile.
More investigation is needed; I'll try to get back to you as soon as I know more.
I'm seeing the same thing with Devise 1.5.1 and devise_openid_authenticatable (1.0.0). Any updates on this?
This problem does not exist if I downgrade Devise to 1.3.4.
Hello everyone! Sorry about the delay in responding to this.
I've just released devise_openid_authenticatable 1.1.0, which drops support for Rails 2/Devise 1.1, and also supports newer versions of Devise without needing database_authenticatable in the mix. As a bonus, the code has become simpler.
Hi,
I'm trying to create an example application using Rails 3.1 and only openid_authenticatable, without database_authenticable. The user model looks like this:
The migration looks like this:
If I go to http://0.0.0.0:3000/users/sign_in
It responds with:
If I add database_authenticatable, the problem goes away, but I'm trying to do without that. My understanding, looking at the example app for Rails 2.x is that this is supported. Right?
I have: