#3838 KCM: If the default ccache cannot be found, fall back to the first one
Closed: Fixed 6 months ago by jhrozek. Opened a year ago by jhrozek.

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

a year ago

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

a year ago

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

9 months ago

Metadata Update from @jhrozek:
- Issue assigned to jhrozek

9 months ago

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

7 months ago

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

6 months ago

Login to comment on this ticket.

Metadata