On 2025-06-23 16:35:35 +0200, raphi wrote: > To be fair, setting up LDAP is very easy in PG, just one line in hba.conf > and all is done. But sadly, that's only where the problems begin. The > difficult part is to embedd this setup into a company, especially a large > one as I work for with over 1000 PG databases and at least that many roles. > Someone needs to be able to manage the passwords in LDAP and this means > someone has to decide who can change which passwords, which is usually where > some sort of Identity and Access Management (IAM) comes into place. > > We already have LDAP and IAM in place in our organization for many other > things, but IAM identities are coupled to a real person, not a team. Which > means only one person in the team would be able to set a new password and > when that person leaves the team, IAM rights need to be revoked and given to > a new person. Doable, but quite a pane in the behind, especially when that > one person happens to be on holidays.
I don't see why that should be the case. You could either grant
privileges to more than one person or - preferrably - to a role which is
then granted to the personal roles.
So for example you would authenticate as «raphi» and I as «hjp» but we
could both change to «foo_admin» or whatever. That would even have the
advantage that we leave an audit trail with our "real" identities.
hjp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | h...@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
signature.asc
Description: PGP signature
