Skip to content
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

Migration to 2.0 #162

Closed
vnazarenko opened this issue Jul 14, 2018 · 2 comments
Closed

Migration to 2.0 #162

vnazarenko opened this issue Jul 14, 2018 · 2 comments

Comments

@vnazarenko
Copy link

Hello, is there any other, more gracefull possibility of migration, except stop/start world. Our system is pretty large, so it's kinda difficult thing to do that

@andrewostroumov
Copy link

We discussed with @vnazarenko and concluded to prepend provider name to encrypted password. So we will have a field in the db without provider nhOG5AqEEGOlJvFmgFYv+g==\n - default mysql_aes_new and with provider active_support:WEhSRFlzV041TlV.... We will migrate whole system to new format and can process multiple providers.

@andrewostroumov
Copy link

andrewostroumov commented Jul 27, 2018

I surprised that every time I update user model password was updated to. This makes this gem useless in production because ActiveSupport::KeyGenerator#generate_key take 100ms every time when user update. Please consider switch from serializers to native setters.

@jmazzi jmazzi closed this as completed Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants