Saving cookies when switching EC2 Ruby on Rails instances

My team is coming to the end of a massive revision of changes in our system and is preparing to make a big switch.

We are currently hosted on AWS using Elastic IP. Our stack is Ruby on Rails, and we use capistrano. We also have a Blackberry app and an iPhone app live and in the hands of customers. Authentication between applications and the server is via cookies, not any authentication key.

I am well aware that this is not the best authentication method, but the old code is deprecated.

Due to the nature of our company and service, IMPERATIVE, when we switch, users do not log out and the session passing through the cookie from the mobile application to the server is respected.

I tried the following approaches:

Point DNS to a different IP address. Point Elastic IP to another AWS instance.

In each case, cookies do not seem to deserve attention.

I am a developer, not a system administrator, and I have run out of ideas. Is there a way to make a new instance a cookie check using Devise on Rails or via AWS? Or another option that I should consider?

+5
source share
1 answer

HTTP Cookies IP- . ( ) . , IP- , , . - IP- IP- DNS-. , .

, : ? Rails? , , .

Rails - cookie ( ), "" , secret_token . , ? , (config/initializers/secret_token.rb) cookie, , .

, , - .

+3

All Articles