Bug 1461899

Summary: Loading enterprise principals doesn't work with a primed cache
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Hrozek <jhrozek>
Component: sssdAssignee: Varun Mylaraiah <mvarun>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: enewland, fidencio, grajaiya, jhrozek, lslebodn, mkosek, mvarun, mzidek, pbrezina, sgoveas, tscherf
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.16.0-15.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 17:11:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Console output and krb5_child log none

Description Jakub Hrozek 2017-06-15 14:24:13 UTC 
This bug is created as a clone of upstream ticket:
https://pagure.io/SSSD/sssd/issue/3431

The IPA subdomains code only loaded the naming suffixes when the subdomains changed. As effect, just restarting sssd breaks logins with enterprise principals.

The workaround is to remove the cache.
Comment 3 Jakub Hrozek 2017-06-21 09:31:05 UTC 
master: fcfc1450a846519f2c74e864a12fad65aa54189b
Comment 19 Lukas Slebodnik 2018-01-23 17:29:35 UTC 
master:
* a8a3fcbf6f75a7c2665e8bf503c186e07dfab333

sssd-1-14:
* 76957f07f79fb30634d2b5b4bed56cf30307c079
Comment 24 Varun Mylaraiah 2018-01-30 12:56:14 UTC 
Created attachment 1388387 [details]
Console output and krb5_child log

Verified 
sssd-1.16.0-15.el7.x86_64

Now, "enterprise principal [true]", with UPN being used.


Attaching krb5_child log and Console output
Comment 27 errata-xmlrpc 2018-04-10 17:11:33 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/RHEA-2018:0929