Under some circumstances (perhaps related to a February Windows 10
update), Leash can get past the krb5_cc_get_principal() step when
processing an empty MSLSA ccache, and get a KRB5_CC_NOMATCH error from
krb5_cc_start_seq_get(). Do not display a modal error dialog if this
happens.
ticket: 8790
tags: pullup
target_version: 1.17-next
}
code = pkrb5_cc_start_seq_get(ctx, cache, &cur);
if (code) {
- functionName = "krb5_cc_start_seq_get";
+ // MSLSA errors here if no TGT is found; suppress error message box
+ code = 0;
goto cleanup;
}
if (*ticketInfoTail)