#3910 KCM destroy operation returns KRB5_CC_NOTFOUND, should return KRB5_FCC_NOFILE if non-existing ccache is about to be destroyed
Closed: Fixed a year ago by jhrozek. Opened a year ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla: Bug 1622008

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

ssia, mostly. When the KCM destroy operation is called, it receives a name as an input. If the name cannot be found, we would currently return KRB5_CC_NOTFOUND. But other ccache types return KRB5_FCC_NOFILE in that case and e.g. utilities like kdestroy special case KRB5_FCC_NOFILE to be non-fatal.

We should fix the return code and perhaps check other codepaths that resolve a name as well.


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

a year ago

Metadata Update from @jhrozek:
- Issue tagged with: KCM, PR, bug

a year ago

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

a year ago

Login to comment on this ticket.

Metadata