> -----Ursprüngliche Nachricht----- > Von: Laurenz Albe <laurenz.albe@xxxxxxxxxxx> > Gesendet: Freitag, 15. Januar 2021 17:21 > An: Zwettler Markus (OIZ) <Markus.Zwettler@xxxxxxxxxx>; pgsql- > general@xxxxxxxxxxxxxx > Betreff: Re: ldap connection parameter lookup > > On Fri, 2021-01-15 at 14:09 +0000, Zwettler Markus (OIZ) wrote: > > I want to use ldap to lookup the connection parameters: > > https://www.postgresql.org/docs/12/libpq-ldap.html > > > > > > Do I have to create one static entry per database within pg_service.conf like: > > > > [mydatabase] > > > ldap://ldap.mycompany.com/dc=mycompany,dc=com?description?one?(cn=mydat > abase) > > > > > > or is there also some kind of generic variant like this (meaning lookup connection > parameters for the database name I tell you somehow): > > > > [${PGDATABASE}] > > > ldap://ldap.mycompany.com/dc=mycompany,dc=com?description?one?(cn=${PGD > ATABASE}) > > I proposed something like that a while ago: > https://postgr.es/m/D960CB61B694CF459DCFB4B0128514C2F3442B%40exadv11 > .host.magwien.gv.at > but it was rejected. > > Perhaps you could come up with a better version. > > Yours, > Laurenz Albe > -- > Cybertec | https://www.cybertec-postgresql.com I'm afraid not. My proposal is as close to yours. Anyway. PostgreSQL needs some kind of generic central name resolution service. It is not feasible to do static entries per database in a large environment with hundreds of clients. It's also not feasible to have ordinary endusers have to handle this static entry by themselves. So Tom, lets give it a try? Regards, Markus
