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:

When enrolling a client with an existing /etc/krb5.keytab, the ipa-client-install appends the new keys to the keytab file without a warning

Version-Release number of selected component (if applicable):
4.5.0-21

How reproducible:
Always

Steps to Reproduce:
1. Find a system with an existing Keytab file
2. Enroll the System with ipa-client-install to an IPA environment
3. Use ktutil -> rkt -> l and find the keys appended

Actual results:
See reproducer

Expected results:
ipa-client-install should warn the user about an existing keytab file and let the user choose to either overwrite the keytab or append the new keys


Additional info:

Need more information on what problem(s) this causes. Are they trying to re-use the same realm name? What errors are being seen?

I guess we can add a logic that would check content of the krb5.keytab and decide to warn if it contains keys from a different realm than IPA. I doubt we should be erroring on them because it actually might be useful in some complex cases to allow keys from multiple realms in the same keytab (with a tuned sssd.conf to pick up proper keys by name).

Upstream ticket:
https://pagure.io/freeipa/issue/7269

component changed from IPA to ansible-freeipa.
--
There is no plan, priority or team capacity now or in the near future for a Red Hat engineer to work on this request. Thus, i am closing the ticket as wontfix or upstream (in case there is an upstream ticket that the community can help us solve). 

We might revisit this decision according to our product goals. Ping tapazogl / Theo in GChat if you need any further clarification. Thank you for reporting this bug/feature.
---