New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devise session reset on subsequent request #3623
Comments
Are you doing sign up with ajax or something like that? In any case, it is very hard to find out what is wrong with such a code snippets, so Can you please provide a sample application that reproduces the error? |
No Ajax. I am new to Git, should I set up a new repo for this? I used git mainly only to push something. |
I already undergone several test in different rails version. And, the strange thing is not in the devise itself, but rather in MongoDB, or should i say... mongoid? If a mongo db is shared by two different app... what happen is that, you can login (under same devise configuration) but the session won't persist. I don't know if this is a mongo/rails/devise problem... |
I confirm that there's problem with sharing mongodb database for devise's user login. I used an entirely new project, new, as in "rails new." First, with a separate database, everything is OK. Then, I changed the db to use the same mongoid db, and then problem begin to occur: that is, session not persisted. Strange... |
@saveav Are you still seeing this issue? I am using Devise and Mongoid and may have a similar problem - I seem to be losing authenticated state within Warden. Trying to work out if this is related. |
Which mongoid version are you using? It was a mongoid bug which should hopefully be fixed. |
Using Mongoid 4.0.2. So this should be fixed in Devise 3.5.2? |
I used:
Devise (3.5.1)
Omniauth (1.2.2)
Warden (1.2.3)
On a trial project, a new one using Mongoid as the ORM. Sessions controller are created anew, and used, instead of the Devise's standard, and changed into:
My session (
whatever
) is persisted, but Warden's session is reset on subsequent request. I don't know why.The text was updated successfully, but these errors were encountered: