-
Notifications
You must be signed in to change notification settings - Fork 84
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
Session stickiness required in multi node HA deployment #37
Comments
Hi sharma-manish - thanks for reaching out. Why do you think it requires session stickiness? The key-value-store used should be in sync with all cluster nodes. So that given it doesn't matter on which instance you request will be processed. Does this make sense? For more information about cluster state snyc see the following link: |
Lets assume you have a 5 node cluster spread across different data centres for HA and DR. The key value store can be "synced" across cluster nodes, but it is going to have some latency. We have tried running our application without session stickiness and observed these issues. We were then told to enable session stickiness to work around this. |
I understand your point. So the request would be to be able to turn the opaque cookie on and off. So the access_token will be send as a cookie instead of the opaque session reference? |
The OIDC plugin requires session stickiness to be enabled in case of highly available deployment topology. This is an anti pattern. Can something be done for removing this dependency?
Browsers typically send request for multiple resources for a site in parallel. In a multi node deployment with round robin load balancing algorithm, the login process can potentially get triggered for multiple requests.
The text was updated successfully, but these errors were encountered: