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.
This bug is created as a clone of upstream ticket:
https://pagure.io/SSSD/sssd/issue/3395
IPA offers the promptusername option to indicate to applications which use information from the Smartcard to find a suitable user for authentication that an optional user name prompt should be shown or not.
This is needed in environments where a certificate is mapped to multiple accounts.
Since pam_sss is one of those applications if used with the 'allow_missing_name' option it should act accordingly.
Verified.
Version ::
sssd-1.15.2-43.el7.x86_64
Results ::
Test first with prompt=False:
- card=[1 valid], certusers=[user1], testuser=None -> PASS
PASS - logs in a user1 without prompt for username
- card=[1 valid], certusers=[user1, user2], testuser=None -> FAIL
PASS - Failed as expected and did not ask for pin.
Test next with prompt=True:
- card=[1 valid], certusers=[user1], testuser=None -> PASS
This one is being handled in bug #1448503
- card=[1 valid], certusers=[user1, user2], testuser=user1 -> PASS
PASS
- card=[1 valid], certusers=[user1, user2], testuser=user2 -> PASS
PASS
- card=[1 valid], certusers=[user1, user2], testuser=user3 -> FAIL
PASS - Failed as expected
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, 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/RHEA-2017:2294