3 ms·

I think it's a bad idea for a database to start implementing third-part vendor related features. That's the type of feature that should be implemented as a plu

I think it's a bad idea for a database to start implementing third-part vendor related features. That's the type of feature that should be implemented as a plugin.

nijave 7y ago
You could just call it "ldap authentication". AD comes with an LDAP interface.
- jtdev 7y ago
  Yes, and that AD LDAP interface is riddled with MS specific deviations that require complying with MS’s way of doing LDAP.
- fanf2 7y ago
  Or Kerberos authentication (which AD also supports) https://www.postgresql.org/docs/current/gssapi-auth.html https://www.postgresql.org/docs/current/gssapi-auth.html
- anarazel 7y ago
  Postgres does have ldap based auth, and also can authenticate against AD using sspi/gssapi. The problem with that is that it requires users to have been created inside postgres first, and that you can't manage group membership inside AD.
  - gregn610 7y ago
    yup, that's what I meant by authorisation, keeping the roles and groups in pgsql up to date.