Set devise stretches to default 10 #567
Open
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
I was running into a problem where logging in with a Spree user created after installing this gem was taking around 120 seconds to login in development. I _think_ this was because the devise stretches was set to 20. See this thread for more context heartcombo/devise#1184 (comment). Perhaps when this initializer was set up originally a different encryption strategy was being used and the higher stretches wasn't as slow. To get around the issue while using this gem, just override the stretches config in a `config/devise.rb` initializer in the host app.
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.
I was running into a problem where logging in with a Spree user created after installing this gem was taking around 120 seconds to login in development. I think this was because the devise stretches was set to 20. See this thread for more context heartcombo/devise#1184 (comment).
Perhaps when this initializer was set up originally a different encryption strategy was being used and the higher stretches wasn't as slow.
To get around the issue while using this gem, just override the stretches config in a
config/devise.rbinitializer in the host app.