Skip to content
This repository has been archived by the owner on Apr 24, 2022. It is now read-only.

Fix Devise payload on production #17

Open
georgiana-b opened this issue Oct 27, 2016 · 3 comments
Open

Fix Devise payload on production #17

georgiana-b opened this issue Oct 27, 2016 · 3 comments
Labels

Comments

@georgiana-b
Copy link
Member

georgiana-b commented Oct 27, 2016

On production, Devise sends and expects authentication payload to be

{
    "email": "[email protected]"
}

instead of

{
    "user": {
        "email": "[email protected]"
    }
}

Extra facts:

  • Doesn't happen on development
  • It has happened before but I can't remember how I fixed it
  • It broke again out without any changes to authentication or User
@nightsh
Copy link
Member

nightsh commented Apr 16, 2017

Is this still a thing?

@georgiana-b
Copy link
Member Author

georgiana-b commented Jul 28, 2017

This issue is caused by the fact that this Mongoid setting doesn't apply in production.

Unfo this can't be easily fixed now because frontend made a workaround in the meantime. I'll come back to this is less critical times.

@nightsh
Copy link
Member

nightsh commented Sep 21, 2017

I would close this with a "won't fix" resolution, since we're going to change both the backend and the auth mechanics. Doesn't seem to me like an issue worth considering now. Agreed?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants