Set warden user before authenticating #53
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Set the warden user with
warden.set_user(@user)before attempting to runwarden.authenticate!(auth_options).Why?
When trying to set up
devise-passwordlesson my app, I couldn't log in after clicking the login link.After further investigation, I noticed that the problem was that the auth_options for my app didn't contain any information related to the user, other than the
:scope => :user.Are there any side effects or bugs people should be aware of?
No. If
wardenfails to set a user, this means that there is no user with the given email to begin with, and the warden user would just benil.The
showaction would then proceed to attempt to authenticate just as always.