Reference my earlier thread "A Debian Head-Scratcher"
Do I file the bug here https://pagure.io/freeipa/issues ? Debian 10, freeipa-client 4.7.2-3 amd64 ______________________________________________________________________________________________
Daniel E. White daniel.e.white@nasa.govmailto:daniel.e.white@nasa.gov NICS Linux Engineer NASA Goddard Space Flight Center 8800 Greenbelt Road Building 14, Room E175 Greenbelt, MD 20771 Office: (301) 286-6919 Mobile: (240) 513-5290
On ke, 04 maalis 2020, White, Daniel E. (GSFC-770.0)[NICS] via FreeIPA-users wrote:
Reference my earlier thread "A Debian Head-Scratcher"
Do I file the bug here https://pagure.io/freeipa/issues ? Debian 10, freeipa-client 4.7.2-3 amd64
There are several issues with Debian support and they need to be addressed by Debian people because that distribution lacks a unified method of programmatically managing PAM configuration (and not only that). I'd suggest you opening a bug against Debian itself.
Any contribution is welcome, of course, but to be clear: opening an issue at FreeIPA pagure will not mean anybody will work on it at all. FreeIPA team has no Debian developers and the only brave maintainer on Debian side (Timo) also would definitely benefit from additional help.
See /var/lib/dpkg/info/libpam-sss.postinst; when the libpam-sss package is installed, "pam-auth-update" is run, which normally updates the various /etc/pam.d/common-* files based on the contents of /usr/share/pam-configs.
If your PAM config files got screwed up for whatever reason, you should be able to run "pam-auth-update" to fix things. If it detects that any of the common-* files were modified outside of its control, it should print a warning advising you to re-run it with --force to blow those changes away and get things working again.
freeipa-users@lists.fedorahosted.org