#3769 sssd tools don't handle the implicit domain
Closed: Fixed 2 years ago by jhrozek. Opened 3 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla: Bug 1599207

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
When no sssd.conf exists, sssctl can not read objects from the cache. Once a
domain has been configured in the configuration file, objects can be pulled
from the cache without any issue.

# grep tuser /etc/passwd

# getent -s sss passwd tuser

This works ok.

# sssctl user-show tuser
(Mon Jul  2 12:13:46:258395 2018) [sssd] [confdb_get_domains] (0x0010): No
domains configured, fatal error!
(Mon Jul  2 12:13:46:258603 2018) [sssd] [sss_tool_route] (0x0010): Command
initialization failed [2] No such file or directory

This does not work. At this time, no sssd.conf exists. This is the default
behaviour after a fresh installation.

# ll /etc/sssd/sssd.conf
ls: cannot access '/etc/sssd/sssd.conf': No such file or directory

Next let's create a basic config file with a single domain using SSSD FILES

# cat /etc/sssd/sssd.conf
services = nss, ifp, pam
domains = files

id_provider = files

# chmod 600 /etc/sssd/sssd.conf
# systemctl restart sssd

sssctl can now read from the cache:

# sssctl user-show tuser
Name: tuser
Cache entry creation date: 07/02/18 12:21:07
Cache entry last update time: 07/02/18 12:21:07
Cache entry expiration time: Expired
Initgroups expiration time: Initgroups were not yet performed
Cached in InfoPipe: No

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:
sssctl can not read from the cache.

Expected results:
sssctl can read from the cache without the need to explicitly configure a
domain for the FILES provider first.

Additional info:

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1599207

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.0

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

3 years ago

Metadata Update from @thalman:
- Issue assigned to thalman

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

2 years ago

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4775

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.