Dear Andre,
Thank you very much for your help.
I think I was missing an important command in the equation.
sudo realm --verbose join ad.corp.com --user=Administrateur --user-principal=postgres/UBUNTU.ad.corp.com@xxxxxxxxxxx
The Linux server as joint the AD and now, psql connection work very well from the clients!
It makes a lot of things that I'm not accustomed too, but was very interesting. I'll also look forward to the other authentication
method that you've talked (PAM).
With best regards,
De : Andre Piwoni <apiwoni@xxxxxxxxx>
Envoyé : 1 mars 2019 11:44 À : Jean-Philippe Chenel Cc : pgsql-general@xxxxxxxxxxxxxxxxxxxx Objet : Re: PostgreSQL (linux) configuration with GSSAPI to a Windows domain Hi Philippe,
I would increase logging level to debug since it is hard to tell from log what is happening.
Have you verified kinit for the user on the server? Sounds like you did since you are running client on the server
Also, my username in postgres database is lowercase without realm info.
At the high level, here's the setup I had:
My setup for PAM is using SSSD PAM module and is configured for AD:
cat
/etc/pam .d /postgresql #%PAM-1.0 auth
required pam_sss.so account
required pam_sss.so
By joining domain using realm sssd you should have krb5.conf and sssd.conf generated for you automatically. You should remove existing krb5.conf before joining domain.
cat /etc/sssd/sssd .conf [sssd] config_file_version
= 2 services
= nss, pam ad_domain
= ad.corp.com krb5_realm
= AD.CORP.COMrealmd_tags
= manages-system joined-with-samba cache_credentials
= True id_provider
= ad krb5_store_password_if_offline
= True default_shell
= /bin/bash ldap_id_mapping
= True use_fully_qualified_names
= False fallback_homedir
= /home/ %u access_provider
= ad On Fri, Mar 1, 2019 at 7:59 AM Jean-Philippe Chenel <jp.chenel@xxxxxxx> wrote:
|