#3838 KCM: If the default ccache cannot be found, fall back to the first one
Opened 3 months ago by jhrozek. Modified 6 days ago

KCM stores the default ccache in a separate DB entry. If the DB entry contains a UUID that cannot be found in the DB for whatever reason, we should just use the first ccache as the default. (This is what we already do if there is no default)


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

2 months ago

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

2 months ago

Metadata Update from @jhrozek:
- Issue tagged with: PR

6 days ago

Metadata Update from @jhrozek:
- Issue assigned to jhrozek

6 days ago

Login to comment on this ticket.

Metadata