| From: | Morten Bonnerup Rasmussen <morten(dot)rasmussen(at)bestseller(dot)com> |
|---|---|
| To: | "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | pgAdmin in Kubernetes vs master password |
| Date: | 2024-10-11 08:30:36 |
| Message-ID: | AS8PR07MB91342BD8EC5838E0E1599ED8E6792@AS8PR07MB9134.eurprd07.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi
We are working on offering pgAdmin as a centrally managed tool to our developers.
It is deployed in Kubernetes, based on this guide, with OAUTH2 enabled (Entra ID):
Deploying pgAdmin on Kubernetes | EDB (enterprisedb.com)<https://www.enterprisedb.com/blog/how-deploy-pgadmin-kubernetes>
But when the service is restarted, we get the master password prompt.
I get this and can provide it. But if one of our developers is the first one to connect and they are prompted, this becomes problematic. They have no idea what the master password is.
What is the best way to manage this challenge?
We could disable usage of master password, but it looks like this would reduce security.
Is it not possible to save it as a secret and provide as a parameter during startup, similar to the default pgadmin user/password?
MORTEN BONNERUP RASMUSSEN
TECH RELIABILITY SERVICES / SPECIALIST
P
+4599423174
M
+4530853174
E
MORTEN(dot)RASMUSSEN(at)BESTSELLER(dot)COM<mailto:morten(dot)rasmussen(at)bestseller(dot)com>
W
BESTSELLER.COM<http://bestseller.com>
BESTSELLER A/S
FREDSKOVVEJ 1, 7330 BRANDE
DENMARK
[cid:eefe2496-3470-4a4d-867c-cf56bae1f259]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Subhradeep Bhowmik | 2024-10-11 11:57:05 | Cannot Start PgAdmin 4 |
| Previous Message | Vikas Dhiman | 2024-10-04 14:06:03 | Re: Getting 404 error |