This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2173040 - [RFE] - print parsed kerberos config
Summary: [RFE] - print parsed kerberos config
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: krb5
Version: 9.3
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Julien Rische
QA Contact: Michal Polovka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-23 19:15 UTC by Jaqueline
Modified: 2023-09-18 22:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 22:41:37 UTC
Type: Story
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-9498 0 None None None 2023-02-23 19:16:31 UTC
Red Hat Issue Tracker   RHEL-4942 0 None Migrated None 2023-09-18 22:38:05 UTC
Red Hat Issue Tracker RHELPLAN-149848 0 None None None 2023-02-23 19:16:35 UTC

Description Jaqueline 2023-02-23 19:15:22 UTC 
Words from the customer:

1. Proposed title of this feature request.
[RFE] print parsed kerberos config

2. What is the nature and description of the request?
With the flexibility of /etc/krb5.conf.d/Kerberos config settings can be applied from multiple locations.  When troubleshooting remote Kerberos systems having a utility to dump the Kerberos config into a single stream as parsed by the libraries would be handy.

A quick tool to say "here is what your system thinks its Kerberos configuration looks like" would reduce the complexity of parsing out the files by hand.

3. Why does the customer need this? (List the business requirements here).
Troubleshooting Kerberos is messy.

4. How would the customer like to achieve this? (List the functional requirements here)
Some sort of tool that dumps to stdout the equivalent of the parsed configuration.

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
The customer can assist with testing this.

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
The customer is not aware of any upstream bugs on this.

7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
9.3

8. List any affected packages or components.
Kerberos

9. Would the customer be able to assist in testing this functionality if implemented?
The customer can assist with testing this.
Comment 3 Julien Rische 2023-03-06 14:16:26 UTC 
The two main reasons users usually face troubles with krb5 configuration are permissions of custom configuration file and conflicting definitions of a same parameter.

There is currently no silver bullet to detect this kind of issue, but some commands can help.

The following command will concatenate all the standard location configuration file in the parsing order:

# cat /etc/krb5.conf.d/* /var/lib/sss/pubconf/krb5.include.d/* /etc/krb5.conf > full_krb5.conf

In case there are multiple occurrences of a certain parameter, the FIRST OCCURRENCE applies. This behavior tends to create a lot of confusion, because most configuration file types use the opposite behavior.

POSIX or SELinux permission issues may cause calls from the krb5 library to fail because one of the configuration files is not readable by an unprivileged user or application. The following command will show the permissions of configuration files in the standard locations:

# ls -lZ /etc/krb5.conf.d/* /var/lib/sss/pubconf/krb5.include.d/* /etc/krb5.conf

Administrators should make sure all of them are readable by all Kerberos users and applications.

A tool similar to "systemctl cat" could help to detect this kind of issues indeed. However, the fact the krb5 configuration file format is not standard INI format (because of configuration blocks), it would be difficult to implement as a standalone tool.

It is not clear if the MIT krb5 configuration parser could be used to operate this kind of checking in its current state. We will open a ticket upstream to discuss this case.
Comment 6 RHEL Program Management 2023-09-18 22:36:35 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7 RHEL Program Management 2023-09-18 22:41:37 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.