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://fedorahosted.org/freeipa/ticket/6101
Description of problem: [[BR]]
It is not possible to kinit as user after migrating users from one freeIPA server to another. The problem is that after migrating the krbCanonicalName stay unchanged (has old realm). krbPrincipalName is updated correctly.[[BR]]
Steps to reproduce: [[BR]]
1) Install two freeIPA servers[[BR]]
2) Create several users on the first one[[BR]]
3) Set passwords to these users[[BR]]
4) Use migrate-ds to migrate users to the second freeIPA[[BR]]
5) Try to login as migrated user[[BR]]
[[BR]]
Actual result: kinit user returns the following error:
{{{
kinit: Client 't2.COM' not found in Kerberos database while getting initial credentials
}}}
IPA-server version: ipa-server-4.4.0-12.el7.x86_64
Verified the bug on the basis of following steps:
1. Verified that the users are migrated successfully (in my casefrom IPA1 to IPA2)
Run following command on IPA2 after creating 100 users on IPA1:
#ipa migrate-ds --user-container="cn=users,cn=accounts,dc=testrelm,dc=test" ldap://<IPA 1 Server hostname>
2. Verified that users are reflected correctly on both the servers:
# ldapsearch -h `hostname` -Y GSSAPI -b "cn=users,cn=accounts,dc=testrelm,dc=test"
3. Reset the migrated user password on IPA2 from UI. (In my case resetted the password for user test_100 to 'abcd')
4. On IPA2, run the following command
# kinit test_100
Password for test_100:
Password expired. You must change it now.
Enter new password:
Enter it again:
# klist
Ticket cache: KEYRING:persistent:0:0
Default principal: test_100
Valid starting Expires Service principal
09/19/2016 07:59:09 09/20/2016 07:59:09 krbtgt/TESTRELM.TEST
Thus on the basis of above observations marking status of bug to "VERIFIED".
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://rhn.redhat.com/errata/RHBA-2016-2404.html