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 1205160 - Complain loudly if backend doesn't start due to missing or invalid keytab
Summary: Complain loudly if backend doesn't start due to missing or invalid keytab
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Picka
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-24 10:53 UTC by Jakub Hrozek
Modified: 2020-05-02 17:23 UTC (History)
10 users (show)

Fixed In Version: sssd-1.13.0-0.1.alpha.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 11:37:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Verify log for bz (3.61 KB, text/plain)
2015-09-29 13:57 UTC, Pavel Picka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3036 0 None closed Complain loudly if backend doesn't start due to missing or invalid keytab 2020-08-07 22:37:21 UTC
Red Hat Product Errata RHSA-2015:2355 0 normal SHIPPED_LIVE Low: sssd security, bug fix, and enhancement update 2015-11-19 10:27:42 UTC

Description Jakub Hrozek 2015-03-24 10:53:08 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1994

The sssd_be loads the keytab on start and checks for the expected principal. In case the keytab is wrong or the principal is missing, there is no explanation with the default logging, just:
{{{
(Thu Jun 20 17:50:54 2013) [sssd[be[ipa.example.com]]] [load_backend_module] (0x0010): Error (2) in module (ipa) initialization (sssm_ipa_id_init)!
(Thu Jun 20 17:50:54 2013) [sssd[be[ipa.example.com]]] [be_process_init] (0x0010): fatal error initializing data providers
(Thu Jun 20 17:50:54 2013) [sssd[be[ipa.example.com]]] [main] (0x0010): Could not initialize backend [2]
}}}

We should make it clear that the back end didn't start due to wrong keytab.

Comment 4 Pavel Picka 2015-09-29 13:57:44 UTC
Created attachment 1078354 [details]
Verify log for bz

Verified

sssd-1.13.0-35.el7.x86_64

Comment 5 errata-xmlrpc 2015-11-19 11:37:02 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://rhn.redhat.com/errata/RHSA-2015-2355.html


Note You need to log in before you can comment on or make changes to this bug.