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

HA: Server affinity should not be required on load balancer #2008

Closed
PaulStovell opened this issue Sep 18, 2015 · 2 comments
Closed

HA: Server affinity should not be required on load balancer #2008

PaulStovell opened this issue Sep 18, 2015 · 2 comments
Assignees
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Milestone

Comments

@PaulStovell
Copy link
Member

When a HA instance is configured, and a user signs in, we issue them a cookie. However the next request may go to another server, which will not recognise the cookie (because of how cookie encryption works) and so the cookie will be rejected.

A temporary workaround is to enable client affinity in the load balancer so that the user always gets the same server (as much as is possible).

We should be able to either issue a cookie and have it work on both servers (using the master key as the basis for any encryption), or find some other way to share it.

@PaulStovell PaulStovell added the kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time label Sep 18, 2015
@PaulStovell PaulStovell changed the title HA: Cookies do not work without server affinity on load balancer HA: Server affinity should not be required on load balancer Sep 18, 2015
@tothegills tothegills self-assigned this Nov 25, 2015
@octoreleasebot octoreleasebot added this to the 3.2.10 milestone Dec 9, 2015
@octoreleasebot
Copy link

Release Note: Server affinity is no longer required for High Availability servers behind a load balancer

@lock
Copy link

lock bot commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Projects
None yet
Development

No branches or pull requests

4 participants