Bug 2009245

To elaborate a bit:

(In reply to Steeve Goveas from comment #0)
> Description of problem:
> 
> TGT active / not active:
> In 8.4:
> 28802]] [k5c_check_old_ccache] (0x4000): Ccache_file is [FILE:/tmp/krb5cc_2001_LI2HRD] and is not active and TGT is  valid.
> 28802]] [k5c_precreate_ccache] (0x4000): Recreating ccache
>
> In 8.5:
> 29437]] [k5c_check_old_ccache] (0x4000): Ccache_file is [FILE:/tmp/krb5cc_2001_dd3Df6] and is  active and TGT is  valid.
> 
> Steps to Reproduce:
> https://gitlab.cee.redhat.com/sssd/sssd-qe/-/blob/RHEL8.5/client/
> krb_provider/krb_tgt_renewal/tgt_renewal#L3
> 
> Actual results:
> 1. Old ccache is not deleted
> 2. tgt is active with no active session
> 
> 
> Expected results:
> If old session is active old ccache should be updated and not create a new
> one


Mentioned tests expects: there is no active session => krb5_child should delete old ccache and create new one

There are two issues observed:
1) `check_if_uid_is_active()` returns incorrect result ("Ccache_file is ... is  active")
this should force SSSD to re-use this cache and then
2) SSSD creates a new ccache (when it is expected that old ccache should be reused)

I propose to use this BZ to track item (2). For this we need a new test that ensures there *is* an active user session to force code path that should re-use ccache.

Perhaps we need additional BZ to track (1)

Looks very similar to bz 1991704

(In reply to Alexey Tikhonov from comment #1)
> 
> There are two issues observed:
> 1) `check_if_uid_is_active()` returns incorrect result ("Ccache_file is ...
> is  active")
> this should force SSSD to re-use this cache and then
> 2) SSSD creates a new ccache (when it is expected that old ccache should be
> reused)
> 
> I propose to use this BZ to track item (2). For this we need a new test that
> ensures there *is* an active user session to force code path that should
> re-use ccache.
> 
> Perhaps we need additional BZ to track (1)

for item (1) - bz 2012263

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days