From: | Andrew Coleman <penguincoder(at)gmail(dot)com> |
---|---|
To: | "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
Subject: | PgAdmin4 behind SSL proxy |
Date: | 2019-06-27 17:14:01 |
Message-ID: | 5d14f954.1c69fb81.e188f.9c5b@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Has anyone had any success running PgAdmin4 behind a reverse proxy? I am using Traefik for routing in my Kubernetes cluster and I am experiencing some strange behavior.
With SSL:
POST /login, cookie is returned with an empty value, GET /browser redirect to /login
Sometimes even requests to /user_management/current_user.js actually returns index.html and causes undefined behavior on the page.
Without SSL, with kubectl port-forward:
POST /login, cookie is returned with a value, GET to /browser returns page contents as expected.
I have set X-Forwarded-Proto to https, but that doesn’t do anything. I have set X-Scheme to https and that helps, but it’s not all the way. Cookies returned do not have the Secure; flag (not sure if that’s necessary, though). I have tried setting the values in this blog post both in config.py and in the environment to no success:
https://blog.miguelgrinberg.com/post/cookie-security-for-flask-applications
I really need to expose PgAdmin via https and not http. Is there any way to do this without so much hate and discontent?
Thanks,
Andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Williams | 2019-06-27 17:40:06 | Re: pgadmin 4 feature behavior change requests |
Previous Message | wambacher | 2019-06-27 15:43:00 | Re: PgAdmin 4.9, no release notes |