Closed andrefmarques closed 3 months ago
First, please migrate to using ghcr.io/authcrunch/authcrunch
. See here.
@andrefmarques , the instances do not share state by design.
There is a cookie with unique session id: AUTHP_SESSION_ID
. Configure the load-balancer with the sticky based on the cookie.
GKE does not support setting your own cookie. BUT, it can generate its own.
Look for the term "Session affinity". See https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-configuration#session_affinity
Describe the issue
I'm using ghcr.io/authp/authp:v1.0.5 with the Caddyfile described bellow to provide an login page to authenticate and access some services. This is deployed on GKE. Everything is worked as expected when using 1 replica, but when there's more than 1 replica the authentication fails, when entering the password or the username.
Configuration
Version Information
Expected behavior
Be able to authenticate when using more than 1 replica
Additional context
Deployed in GKE with Deployment and istio sidecar.