From 148d1fbaa75fb1a89702f5748b6ac7fd96e0927b Mon Sep 17 00:00:00 2001 From: YuviPanda Date: Tue, 15 Feb 2022 17:22:59 +0530 Subject: [PATCH] Fix pgadmin4 for U Texas pgadmin4 was using end user IP in its session cookie for extra security - however this doesn't work in kubernetes type environments with a lot of dynamic IPs. The documentation suggests we turn this off, and we do. Ref https://github.com/2i2c-org/infrastructure/issues/968 --- config/clusters/2i2c/utexas.values.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/config/clusters/2i2c/utexas.values.yaml b/config/clusters/2i2c/utexas.values.yaml index 684d68873..c286edc9a 100644 --- a/config/clusters/2i2c/utexas.values.yaml +++ b/config/clusters/2i2c/utexas.values.yaml @@ -117,6 +117,13 @@ jupyterhub: # FIXME: This doesn't work with named servers, # https://github.com/jupyterhub/kubespawner/pull/565 fixes this value: "/user/{username}/proxy/absolute/5050" + # Turn off tying the user session to a particular IP the request + # is coming from - in a dynamic environment like kubernetes, this + # means users keep getting 'logged out' every minute or so. + # Look for `ENHANCED_COOKIE_PROTECTION` in + # https://www.pgadmin.org/docs/pgadmin4/development/config_py.html + - name: PGADMIN_CONFIG_ENHANCED_COOKIE_PROTECTION + value: 'False' - name: postgres image: postgres:10 resources: