Postgresql 11 SSPI authentication failing

Indeed an empty password is equivalent to no password so it's not going to be accepted by the server when pg_hba.conf says that a password is required.

Still, there are various ways to avoid inputting the password:

• trust method in pg_hba.conf, possibly constrained to a specific user and database
• client-side PGPASSWORD environment variable
• client-side .pgpass file
• dummy password like "test" stored in the same place than the login name

There is two independant steps with Postgres and LDAP:

1. tells Postgres how to query LDAP to authenticate one user, it's documented here . You must use ldap authentication method in pg_hba.conf.
2. You must create the roles in Postgres, with options etc. You can use a tool like ldap2pg or a custom script.

That way, you can manage roles and ACL just as usual. You just don't need to store passwords in cluster.