RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Hello redhat,

I'd like to raise this enhancement request that redhat's PAM implementation supports a local tweaks that won't get overridden by authconfig.

Some chages and tweaks can't be done using pam-config or authconfig - for example proper setting of umask per groups/users eg:

session [default=1 success=ignore] pam_succeed_if.so quiet user ingroup secret-agents
session optional pam_umask.so umask=0077
session [default=1 success=ignore] pam_succeed_if.so quiet uid eq 1005
session optional pam_umask.so umask=0002

^^ this sets an umask 0077 for members of group "secret-agents" and umask 0002 for user with uid 1005 ..

I propose supporting pam.d/system-auth-local, that will be included (sourced) to system-auth (the most important pam.d/ login-related file sourced to the very most of other modules) and that will be by default empty and not overridden by authconfig/pam-config ...

Considering to support more files with suffix -local seems reasonable to me.

Regards, daniel

Authconfig supports different way of local modification (by using symlinks) and I do not think we want to complicate the pam configuration files even more.

(In reply to Tomas Mraz from comment #2)
> Authconfig supports different way of local modification (by using symlinks)
> and I do not think we want to complicate the pam configuration files even
> more.

Can you elaborate that idea about symlinks and authconfig not overriding whatever your setup is ?

I don't see anything complicated on file pam.d/auth-config-local with just a commented out header stating out: here you can put your additional directives my dear sysadmin ..

regards, daniel

See the system-auth-ac(5) manual page for details.