You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
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
The text was updated successfully, but these errors were encountered: