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.

Description of problem:

This is a sub-BZ of BZ #2091979 and related sub-BZ #2099203.
When poly-instantiation is enabled, ssh users cannot log in password-less because the PAM stack is not correct for authentication (see BZ #2099203).
We need a new PAM pam_namespace module to be included in the PAM stack for auth, this should be controlled by this new option.

Version-Release number of selected component (if applicable):

authselect-1.2.3-7.el9.x86_64

How reproducible:

Always

Steps to Reproduce:
1. See reproducer in BZ #2099203

I see Iker wants to implement thread safety first before including this module in authselect, so I will wait for notification that everything is ready and I can move on.

After thorough consideration, pam_namespace is not a module that should be put into generic system-auth or other files managed by authselect. It would cause issues and unexpected behavior.

The system-auth configuration is included in other pam services that may include pam_namespace on their own if it makes sense and at the same time there are services like su where pam_namespace is definitely not desirable.

Thus closing as wontfix.