Bug 2173040
| Summary: | [RFE] - print parsed kerberos config | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jaqueline <jbotelho> |
| Component: | krb5 | Assignee: | Julien Rische <jrische> |
| Status: | CLOSED MIGRATED | QA Contact: | Michal Polovka <mpolovka> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9.3 | CC: | ftrivino |
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-18 22:41:37 UTC | Type: | Story |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jaqueline
2023-02-23 19:15:22 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. 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. 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. |