Hot answers tagged

2

If anyone else encounters this like I did so starting from 9.5 you will need to add an optional parameter both to the ipv4 and ipv6 in order for this to work include_realm=0 so the whole thing will look like host all your_username 127.0.0.1/32 sspi include_realm=0


2

Turns out it was due to a wildly-outdated apt puppet module. Updating the module to apt 2.2.2 to match postgresql 4.7.1 (which I already had) worked as per the documentation.


1

There doesn't seem to be a flag you can pass to configure for this, but inside the script it uses a variable called PGSQL to store its hard-coded assumptions on where to find postgresql. Running configure like this let me change the path and build check_pgsql. PGSQL=/usr/pgsql-9.3 ./configure --therestofyourflagshere


1

Read the Friendly Manual: http://www.postgresql.org/docs/9.5/static/auth-methods.html You probably want to use https://github.com/larskanis/pg-ldap-sync to sync your LDAP users and groups to PostgreSQL


1

Thanks everyone, I just made a change in /var/lib/pgsql/9.4/data/pg_hba.conf with : local all all ldap ldapserver=ldap.server ldapport=389 ldaptls=0 ldapprefix="uid=" ldapsuffix=",ou=People,dc=domain,dc=com" And the authentication works!


1

Apr 17 19:46:18 v22015072919626549 postfix/virtual[8844]: 62D6A3E0DC9: to=<***>, relay=virtual, delay=0.05, delays=0.01/0.01/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) So Postfix is delivering the mail somewhere, but we don't yet know where. I am can not receive mails. Sending emails works perfect. So are you sure Postfix delivers ...


1

ok I found out the problem. Going to the file /var/lib/pgsql/data/pg_hba.conf, looking for the line host all all 127.0.0.1/32 ident and replacing ident with trust apparently fixed the issue.


1

You should add host all all 127.0.0.1/32 md5 to your pg_hba.conf and reload PostgreSQL service then.



Only top voted, non community-wiki answers of a minimum length are eligible