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.
Description of problem:
IPA with AD trust.
when a IPA user gets reset, he can not login trough ssh and change the password, (he wont be prompted) , he then have to login to the ipa gui first to change password and then login with ssh.
Version-Release number of selected component (if applicable):
current release
How reproducible:
All the time
Steps to Reproduce:
1. Create a IPA-AD trust
2. Create IPA user.
3. Try and login trough ssh with password
4. change password in gui
5. login again
Actual results:
Failed login attempt
Expected results:
login to server being asked to change password
Additional info:
Log files attached.
It looks like it is related to 'krb5_use_enterprise_principal = True' or the automatic setting of it in the 7.3 version of SSSD.
If the enterprise principal feature is not needed for the AD users the setting 'krb5_use_enterprise_principal = False' in the [domain/...] section of sssd.conf would be a work-around.
To reproduce this outside of SSSD you can call
KRB5_TRACE=/dev/stdout kinit -E -C ipauser -S 'kadmin/changepw'
Assigning to krb5 to get feedback what it the expected behavior here, i.e. requesting 'kadmin/changepw' ticket to change an expired password with an enterprise principal.