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.
DescriptionAlexey Tikhonov
2022-11-27 16:07:26 UTC
This bug was initially created as a copy of Bug #2144491
I am copying this bug because: to track fix for RHEL9
Description of problem:
UPN check cannot be disabled explicitly but requires krb5_validate = false' as a workaround
The first is
that the UPN check cannot be disabled explicitly but requires
'krb5_validate = false' as a work-around, this is already fixed
by the test build provided by Sumit
Version-Release number of selected component (if applicable):
RHEL 8.7
sssd-2.7.3-4.el8_7.1.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Failed login with AD user on IPA client
From sssd_pac.log
-----
* (2022-11-16 6:54:57): [pac] [cache_req_done] (0x0400): [CID#2] CR #0: Finished: Success
* (2022-11-16 6:54:57): [pac] [check_upn_and_sid_from_user_and_pac] (0x0020): [CID#2] UPN of user entry and PAC do not match.
********************** BACKTRACE DUMP ENDS HERE *********************************
(2022-11-16 6:55:08): [pac] [check_upn_and_sid_from_user_and_pac] (0x0020): [CID#4] UPN of user entry and PAC do not match.
* ... skipping repetitive backtrace ...
(2022-11-16 6:55:21): [pac] [check_upn_and_sid_from_user_and_pac] (0x0020): [CID#6] UPN of user entry and PAC do not match.
* ... skipping repetitive backtrace ...
(2022-11-16 6:55:31): [pac] [check_upn_and_sid_from_user_and_pac] (0x0020): [CID#8] UPN of user entry and PAC do not match.
* ... skipping repetitive backtrace ...
(2022-11-16 6:55:43): [pac] [check_upn_and_sid_from_user_and_pac] (0x0020): [CID#10] UPN of user entry and PAC do not match.
-----
Expected results:
With the test build.
------
(2022-11-17 4:03:50): [pac] [check_upn_and_sid_from_user_and_pac] (0x4000): [CID#2] UPN of user entry [abroy.COM] and PAC [Abhijit.Roy.com] do not match, ignored. <---
(2022-11-17 4:03:50): [pac] [sysdb_ldb_msg_difference] (0x2000): [CID#2] Added attr [pacBlob] to entry [name=aduser1.COM,cn=users,cn=AD.EXAMPLE.COM,cn=sysdb]
(2022-11-17 4:03:50): [pac] [sysdb_set_entry_attr] (0x0200): [CID#2] Entry [name=aduser1.COM,cn=users,cn=AD.EXAMPLE.COM,cn=sysdb] has set [cache, ts_cache] attrs.
------
Now, sssd is able to ignore the `UPN of user entry [abroy.COM] and PAC [Abhijit.Roy] do not match, ignored`
Additional info:
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 (sssd 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-2023:2514