Bug 874618

Summary:	sss_cache: fqdn not accepted
Product:	Red Hat Enterprise Linux 6	Reporter:	Dmitri Pal <dpal>
Component:	sssd	Assignee:	Jakub Hrozek <jhrozek>
Status:	CLOSED ERRATA	QA Contact:	Kaushik Banerjee <kbanerje>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	apeetham, grajaiya, jgalipea, pbrezina, tlavigne
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sssd-1.9.2-61.el6	Doc Type:	Bug Fix
Doc Text:	Cause: sss_cache utility did not accept fully qualified domain name. Consequence: Administrator was unable to force expiration of a user record in sssd cache with fully qualified domain name. Fix: sss_cache utility accepts fully qualified domain name. Result: Administrator is able to force expiration of a user record in sssd cache with fully qualified domain name.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 09:39:55 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:
Bug Depends On:
Bug Blocks:	895654

Description Dmitri Pal 2012-11-08 14:32:08 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1620

sss_cache does not accept fully qualified names.

How to reproduce (for example):
1. run sssd
2. getent passwd user
3. sss_cache -u user

Result:
No matching object found in the cache.

Expected result:
user from domain example.com should be removed from cache.

Comment 1 Jakub Hrozek 2013-01-03 13:10:25 UTC

There is a patch on the list.

Comment 3 Amith 2013-01-24 16:36:48 UTC

Verified and automated the BZ in SSSD Version: sssd-1.9.2-82.el6.x86_64

As expected, sss_cache works fine with fqdn of users without errors. The user also gets invalidated from Cache.

Comment 4 errata-xmlrpc 2013-02-21 09:39:55 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.

http://rhn.redhat.com/errata/RHSA-2013-0508.html