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/freeipa/issue/7502

### Possible Issue
Testing shows that if a user is required to change their password on next login (after a password reset for example), then authenticating to the UI with a certificate will fail.


#### Steps to Reproduce
1. Perform a password reset for <user>
2. From a machine with <user>'s certificate imported into Firefox, attempt to log in to the UI using certificate - fails
3. kinit <user>
  # set a new password
4. Attempt login to UI with certificate again - succeeds


#### Actual behavior
Login fails

#### Expected behavior
Login succeeds

#### Version/Release/Distribution
$ rpm -q freeipa-server freeipa-client ipa-server ipa-client 389-ds-base pki-ca krb5-server
package freeipa-server is not installed
package freeipa-client is not installed
ipa-server-4.5.0-20.el7.x86_64
ipa-client-4.5.0-20.el7.x86_64
389-ds-base-1.3.6.1-16.el7.x86_64
pki-ca-10.4.1-10.el7.noarch
krb5-server-1.15.1-8.el7.x86_64



I wanted to know whether this was by design as I would have thought that the password login and certificate login methods should operate independently.

Creating a doc bug out of an issue reported upstream. The jist is:

From a Kerberos perspective, what's happening here is that the principal has the +needchange flag set. The historical meaning of this flag is that the principal will be locked out of authenticating to all services except kadmin/changepw, which allows it to change its password.

Kerberos sort of expects that either users will use a password (e.g., with encrypted timestamp or SPAKE) or they will use a certificate (pkinit). We're therefore disinclined to change this behavior since we don't expect users to encounter it, and the necessity for change of password is considered "high priority".

Windows Integration Guide, Linux Domain Identity, Authentication, and Policy Guide und System-Level Authentication Guide sind live

The update is now available on the Customer Portal.