Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 2005526

Summary:	authselect with-smartcard-required breaks cron
Product:	Red Hat Enterprise Linux 8	Reporter:	Orion Poplawski <orion>
Component:	cronie	Assignee:	Jan Staněk <jstanek>
Status:	CLOSED ERRATA	QA Contact:	Jan Houska <jhouska>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	hhorak, jstanek, opohorel
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	cronie-1.5.2-6.el8	Doc Type:	Bug Fix
Doc Text:	Cause: Upstream briefly changed the PAM settings for crond to use only password authentication for non-root users. Consequence: When other form of authentication were required by the system (i.e. smartcard authentication), crond failed to authorize the user even with right credentials. Fix: Upstream patch was backported that changed the PAM settings to use whatever authentication method were configured on the system. Result: A regular user can now be authenticated to utilize cron with any configured PAM authentication method.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 15:18:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Orion Poplawski 2021-09-17 22:27:07 UTC

Description of problem:

It appears upstream briefly changed the crond pam configuration to use "password-auth" rather than "system-auth".  This breaks cron for users when smartcard auth is required.

PAM ERROR (Failure setting user credentials)

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

Upstream reverted this here: https://github.com/cronie-crond/cronie/commit/978a00ea7ac92852c153ebb3b2152886730ca51c
which is in 1.5.3.

Version-Release number of selected component (if applicable):
cronie-1.5.2-4.el8.x86_64

Comment 6 Jan Staněk 2021-10-12 11:18:09 UTC

Fix commited in dist-git [1] and built in brew [2].

[1]: http://pkgs.devel.redhat.com/cgit/rpms/cronie/commit/?h=rhel-8.6.0&id=e55478fdad56bfd8f856de604f2641bc2eac5cba
[2]: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1747601

Comment 14 errata-xmlrpc 2022-05-10 15:18:28 UTC

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 (cronie 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:2007