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.
Bug 1503022 - ipa-getkeytab man page should have more details about consequences of krb5 key renewal
Summary: ipa-getkeytab man page should have more details about consequences of krb5 ke...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-17 08:19 UTC by Thorsten Scherf
Modified: 2018-04-10 16:49 UTC (History)
7 users (show)

Fixed In Version: ipa-4.5.4-7.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 16:48:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0918 0 None None None 2018-04-10 16:49:12 UTC

Description Thorsten Scherf 2017-10-17 08:19:36 UTC 
Description of problem:

The 'ipa-getkeytab' tool is used to retrieve a kerberos keytab from the server. The man page contains a warning that retrieving the keytab resets the secret for the Kerberos principal and that this renders all other keytabs for that principal invalid.

Some more details why resetting the key in a replicated environment might be not the best idea should be added to the man page.

https://www.freeipa.org/page/V4/Keytab_Retrieval can be used as a reference.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Florence Blanc-Renaud 2017-11-07 08:29:20 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/7237
Comment 3 Standa Laznicka 2017-11-08 07:01:24 UTC 
Fixed upstream
master:
https://pagure.io/freeipa/c/8b8437aa7342a79169913c886af4ac35f253aee2
Comment 4 Standa Laznicka 2017-11-08 09:51:54 UTC 
Fixed upstream
ipa-4-5:
https://pagure.io/freeipa/c/1f7ffb1ad0d4f5769494ae69a828788a5b90e6db
Comment 5 Standa Laznicka 2017-11-09 11:10:10 UTC 
Fixed upstream
ipa-4-6:
https://pagure.io/freeipa/c/e76ab3e8b08a4b4d08f05208117be38e383fa0a6
Comment 7 Mohammad Rizwan 2018-01-18 10:05:46 UTC 
version:
ipa-server-4.5.4-8.el7.x86_64

steps:
1. $ man ipa-getkeytab

Actual result:

[..]
WARNING:  retrieving the keytab resets the secret for the Kerberos principal.  This renders all other keytabs for that principal invalid.  When multiple hosts or
       services need to share the same key (for instance in high availability or load balancing clusters), the -r option must be  used  to  retrieve  the  existing  key
       instead of generating a new one (please refer to the EXAMPLES section).

       Note  that  the  user or host calling ipa-getkeytab needs to be allowed to generate the key with ipa host-allow-create-keytab or ipa service-allow-create-keytab,
       and the user or host calling ipa-getkeytab -r needs to be allowed to retrieve the keytab for the host or service with ipa host-allow-retrieve-keytab or ipa  ser‐
       vice-allow-retrieve-keytab.
[..]


Based on above observations, marking the bug as verified.
Comment 10 errata-xmlrpc 2018-04-10 16:48:21 UTC 
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://access.redhat.com/errata/RHBA-2018:0918
Note You need to log in before you can comment on or make changes to this bug.