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:

On EL8 with:

Profile ID: sssd
Enabled features:
- with-smartcard
- with-smartcard-lock-on-removal
- with-sudo
- with-custom-automount

A local user (tempmon uid 1000 in /etc/passwd) cannot access cron:

You (tempmon) are not allowed to access to (crontab) because of pam configuration.

pam_sssd:

[pam_reply] (0x0200): Returning [10]: User not known to the underlying authentication module to the client [CID #2872]


Version-Release number of selected component (if applicable):
authselect-1.2.2-3.el8.x86_64
sssd-2.5.2-2.el8_5.4.x86_64

Note that I have also switched the crond auth to system-auth per bug #2005526

Proposed fix upstream:
https://github.com/authselect/authselect/pull/301

Thank you for the patch. Can you please confirm that this scratch build fixes the issue for you? (It is current 8.5 content with your patch applied).

https://pbrezina.fedorapeople.org/scratch/2070325/

Pushed upstream:
- master 5cce90e58b663b5aa2915e263b7c9d0f86945b72
- 1.2.x 804b44ad4d3cea11026b08c86b66de02c95c15a3

It seems to resolve my particular issue.  Hopefully it doesn't break anything else :)

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (authselect bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7738