Hi, No probs in Ubuntu 22.04.1 thats for shore. Ever tired with real thing? SH On 25/08/2022 07:41, Ranbir via FreeIPA-users wrote: > Hello All, > > Has anyone successfully enrolled an Ubuntu 22 client into an AlmaLinux > 9 IdM or Rocky Linux 9 IdM domain in a trust with AD _and_ managed to > have consistently fast and reliable logins into that Ubuntu 22 client > with AD users? I sure haven't. > > I have been smashing my head into a wall trying to get stupid Ubuntu 22 > to work. After enabling debug_level 9, I managed to figure out that my > test client was missing the krb5-pkinit package so I installed that. I > also noticed errors in sssd_pac.log about the backend being offline. I > eventually figured out that I needed to add "services = pac" to the > client's sssd.conf. Note: I had removed the services line because in > Ubuntu 22, the various services are instead started as needed via their > sockets (e.g. sssd-autofs.socket, sssd-nss.socket, etc.). If you leave > them defined in the services line, you get tons of errors during system > startup. > > I've resolved those errors, but I'm still seeing extremely slow logins > when it works. Usually, the login just fails. However, if I login as > root and lookup AD users, they are found and returned to the terminal. > > The sssd.conf from the client running sssd 2.6.3 is below. If anyone > has any pointers, please send them over. I wish I didn't have to get > Ubuntu 22 clients working with freeipa, but I do. :( > > > > [domain/idm.domain.com] > id_provider = ipa > ipa_server = _srv_, p1idma01.idm.domain.com > ipa_domain = idm.domain.com > ipa_hostname = u22test.idm.domain.com > auth_provider = ipa > chpass_provider = ipa > access_provider = ipa > cache_credentials = True > ldap_tls_cacert = /etc/ipa/ca.crt > ldap_deref_threshold = 0 > krb5_store_password_if_offline = True > selinux_provider = none > sudo_provider = ipa > autofs_provider = ipa > subdomains_provider = ipa > session_provider = ipa > hostid_provider = ipa > ipa_automount_location = yow > debug_level = 9 > > [domain/idm.domain.com/corp.ad.domain.com] > ad_site = ottawa > > [sssd] > #services = nss, pam, ssh, sudo, autofs > services = pac > domains = idm.domain.com > debug_level = 9 > > [nss] > default_shell = /bin/bash > homedir_substring = /home > debug_level = 9 > > [pam] > debug_level = 9 > > [sudo] > > [autofs] > > [ssh] > > [pac] > > [ifp] > > [session_recording] > > > > _______________________________________________ > FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org > To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedoraho... > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Hello All, Has anyone successfully enrolled an Ubuntu 22 client into an AlmaLinux 9 IdM or Rocky Linux 9 IdM domain in a trust with AD _and_ managed to have consistently fast and reliable logins into that Ubuntu 22 client with AD users? I sure haven't. I have been smashing my head into a wall trying to get stupid Ubuntu 22 to work. After enabling debug_level 9, I managed to figure out that my test client was missing the krb5-pkinit package so I installed that. I also noticed errors in sssd_pac.log about the backend being offline. I eventually figured out that I needed to add "services = pac" to the client's sssd.conf. Note: I had removed the services line because in Ubuntu 22, the various services are instead started as needed via their sockets (e.g. sssd-autofs.socket, sssd-nss.socket, etc.). If you leave them defined in the services line, you get tons of errors during system startup. I've resolved those errors, but I'm still seeing extremely slow logins when it works. Usually, the login just fails. However, if I login as root and lookup AD users, they are found and returned to the terminal. The sssd.conf from the client running sssd 2.6.3 is below. If anyone has any pointers, please send them over. I wish I didn't have to get Ubuntu 22 clients working with freeipa, but I do. :( [domain/idm.domain.com] id_provider = ipa ipa_server = _srv_, p1idma01.idm.domain.com ipa_domain = idm.domain.com ipa_hostname = u22test.idm.domain.com auth_provider = ipa chpass_provider = ipa access_provider = ipa cache_credentials = True ldap_tls_cacert = /etc/ipa/ca.crt ldap_deref_threshold = 0 krb5_store_password_if_offline = True selinux_provider = none sudo_provider = ipa autofs_provider = ipa subdomains_provider = ipa session_provider = ipa hostid_provider = ipa ipa_automount_location = yow debug_level = 9 [domain/idm.domain.com/corp.ad.domain.com] ad_site = ottawa [sssd] #services = nss, pam, ssh, sudo, autofs services = pac domains = idm.domain.com debug_level = 9 [nss] default_shell = /bin/bash homedir_substring = /home debug_level = 9 [pam] debug_level = 9 [sudo] [autofs] [ssh] [pac] [ifp] [session_recording]

After enabling debug_level 9, I managed to figure out that my test client was missing the krb5-pkinit package so I installed that.

also noticed errors in sssd_pac.log about the backend being offline. I eventually figured out that I needed to add "services = pac" to the client's sssd.conf. Note: I had removed the services line because in Ubuntu 22, the various services are instead started as needed via their sockets (e.g. sssd-autofs.socket, sssd-nss.socket, etc.). If you leave them defined in the services line, you get tons of errors during system startup.

I've resolved those errors, but I'm still seeing extremely slow logins when it works. Usually, the login just fails. However, if I login as root and lookup AD users, they are found and returned to the terminal.

On Thu, 2022-08-25 at 18:44 +0100, Sam Morris via FreeIPA-users wrote: > I thought krb5-pkinit is only needed if you want to use PKINIT? sssd > uses the host/$HOSTNAME principal to establish a FAST channel for > pre-authentication, so I don't see how krb5-pkinit affects things? My goal there was to just get rid of the error. We're not using smartcards so it didn't really matter that an error for the missing shared library was recorded. It's hard to tell when an error in the log is actually just informational or causing other real problems. > > I thought 'services = pac' was the default in Debian & that Ubuntu > would > inherit this? On a fresh Ubuntu 22 host after installing freeipa-client and enrolling it into freeipa, the services line that gets added to sssd.conf contains more than just "pac". That in and of itself is a problem in Ubuntu because the sockets for the responders are enabled by default. After figuring out why I was seeing startup errors in the journal, I nuked the whole line. But, that broke the pac responder and I didn't catch that until a couple of days ago.

> I did try socket-activating the pac responder, but I found that sssd > would always launch its own pac responder in addition to the > socket-activated one, so sssd-pac.socket is left disabled by default. Yes, that's what I ended up doing a couple of days ago. > > This could be caused by Ubuntu's extremely annoying login script that > looks up every member of every AD group that you're a member of when > you > log in. > > https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1863894 > > Apply my modification to my script or just disable it and see if your > logins are any quicker. Ah, that explains why I was seeing in the logs every single user of every group being looked up. I was trying to figure out why Ubuntu was doing that. I surmised it had to do with some customization in Ubuntu's login procedure. I just didn't know where to look. Thank you for that tip. I'll give your changes a shot.