On Fri, Oct 11, 2024 at 2:00 PM Morten Bonnerup Rasmussen < morten.rasmus...@bestseller.com> wrote:
> 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. > > If you are using pgAdmin in web based multiuser mode with OAuth2, we would recommend to use the master password and the reasons are mentioned here: https://www.pgadmin.org/docs/pgadmin4/8.12/master_password.html You can share this documentation with your developers to understand the importance of it. 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 <morten.rasmus...@bestseller.com> > > W > > > BESTSELLER.COM <http://bestseller.com> > > BESTSELLER A/S > > FREDSKOVVEJ 1, 7330 BRANDE > > DENMARK > > > > >
