Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1097286 - Expanding home directory fails when the request comes from the PAC responder
Expanding home directory fails when the request comes from the PAC responder
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd (Show other bugs)
7.0
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Jakub Hrozek
Kaushik Banerjee
: ZStream
Depends On:
Blocks: 1098608
  Show dependency treegraph
 
Reported: 2014-05-13 09:36 EDT by Jakub Hrozek
Modified: 2015-10-01 04:50 EDT (History)
13 users (show)

See Also:
Fixed In Version: sssd-1.11.2-68
Doc Type: Known Issue
Doc Text:
Cause: The code that handles saving user when handling requests on the IPA server failed when the request was a SID-to-name mapping. Consequence: As a result, users who were logging from Windows clients using GSSAPI had their membership set incorrectly as their groups could not be converted from SIDs. Workaround None Result N/A
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 05:27:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
nsoman: needinfo+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0441 normal SHIPPED_LIVE sssd bug fix and enhancement update 2015-03-05 10:05:27 EST

  None (edit)
Description Jakub Hrozek 2014-05-13 09:36:36 EDT
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/2333

When a request for a user is a lookup by SID, typicaly when it comes from the PAC responder, we don't handle the request well and error out. This would be the symptoms:
{{{
[apply_subdomain_homedir] (0x0040): Unsupported filter type: [4]
}}}
Comment 1 Alexander Bokovoy 2014-05-13 09:39:53 EDT
Note that this is severe bug for Windows Server 2012 interoperability. Without the fix in place, no single sign-on is possible with SSSD. This largerly kills the benefit of Kerberos cross-forest trusts.
Comment 2 Jakub Hrozek 2014-05-13 09:43:52 EDT
(In reply to Alexander Bokovoy from comment #1)
> Note that this is severe bug for Windows Server 2012 interoperability.
> Without the fix in place, no single sign-on is possible with SSSD. This
> largerly kills the benefit of Kerberos cross-forest trusts.

Clarification -- the bug *only* hits the SSSD in server mode, not the clients. But I agree this is a bad one and would prevent the AD admins from logging in to the IDM servers.
Comment 3 Jakub Hrozek 2014-05-13 09:49:32 EDT
To reproduce, login with GSSAPI on the IPA client:

ssh -k -l Administrator@AD.REALM `hostname`
Comment 4 Namita Soman 2014-05-13 09:49:32 EDT
Please add steps to reproduce/verify this issue
Comment 5 Namita Soman 2014-05-13 09:50:40 EDT
refreshed page and saw you already added steps - thanks :)
Comment 6 Jakub Hrozek 2014-05-13 09:50:55 EDT
(In reply to Jakub Hrozek from comment #3)
> To reproduce, login with GSSAPI on the IPA client:
> 
> ssh -k -l Administrator@AD.REALM `hostname`

Err, I'm sorry, I meant to say login with GSSAPI on the IPA *SERVER*.
Comment 7 Namita Soman 2014-05-13 11:03:33 EDT
when would response come from PAC responder, versus not from PAC responder?
 
Also please include info about pkg versions for server and client, and /etc/redhat-release to help reproduce.
Comment 8 Namita Soman 2014-05-13 11:09:40 EDT
also - why is the user logging into the server? isn't a ad user typically logging into the client?
Comment 9 Jakub Hrozek 2014-05-13 11:12:33 EDT
(In reply to Namita Soman from comment #7)
> when would response come from PAC responder, versus not from PAC responder?
>  

When logging with GSSAPI

> Also please include info about pkg versions for server and client, and
> /etc/redhat-release to help reproduce.

RHEL7 latest as of today.
Comment 10 Jakub Hrozek 2014-05-13 11:13:01 EDT
(In reply to Namita Soman from comment #8)
> also - why is the user logging into the server? isn't a ad user typically
> logging into the client?

The AD admin might want to perform maintenance on the server.
Comment 13 Jakub Hrozek 2014-05-15 12:19:25 EDT
Proposing for RHEL7 0day
Comment 19 Steeve Goveas 2014-11-24 05:51:49 EST
Verified in version

* Passwordless login on IPA Server

[root@gizmo ~]# rpm -q sssd
sssd-1.12.2-12.el7.x86_64

[root@gizmo ~]# grep ipa_server /etc/sssd/sssd.conf
ipa_server = _srv_, ibm-x3620m3-01.steeve2011.test

[root@gizmo ~]# kdestroy -A

[root@gizmo ~]# echo Secret123 | kinit Administrator@ADTEST.QE
Password for Administrator@ADTEST.QE: 

[root@gizmo ~]# ssh -K -l Administrator@adtest.qe ibm-x3620m3-01.steeve2011.test
Creating home directory for Administrator@adtest.qe.

-sh-4.2$ pwd
/home/adtest.qe/administrator

-sh-4.2$ id
uid=1148400500(administrator@adtest.qe) gid=1148400500(administrator@adtest.qe) groups=1148400500(administrator@adtest.qe),1148400512(domain admins@adtest.qe),1148400513(domain users@adtest.qe),1148400518(schema admins@adtest.qe),1148400519(enterprise admins@adtest.qe),1148400520(group policy creator owners@adtest.qe) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

-sh-4.2$ logout
Connection to ibm-x3620m3-01.steeve2011.test closed.

* Passwordless login on IPA client

[root@gizmo ~]# ssh -K -l Administrator@adtest.qe `hostname`
Creating home directory for Administrator@adtest.qe.

-sh-4.2$ hostname
gizmo.steeve2011.test

-sh-4.2$ klist
Ticket cache: KEYRING:persistent:1148400500:1148400500
Default principal: Administrator@ADTEST.QE

Valid starting       Expires              Service principal
11/24/2014 02:18:03  11/24/2014 12:07:31  krbtgt/ADTEST.QE@ADTEST.QE
	renew until 11/25/2014 02:07:30
Comment 21 errata-xmlrpc 2015-03-05 05:27:57 EST
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/RHBA-2015-0441.html

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