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.rasmus...@bestseller.com<mailto:morten.rasmus...@bestseller.com>

W



BESTSELLER.COM<http://bestseller.com>

BESTSELLER A/S

FREDSKOVVEJ 1, 7330 BRANDE

DENMARK

[cid:eefe2496-3470-4a4d-867c-cf56bae1f259]




Reply via email to