fix: handle case where account entities is empty in after cache access

[LuccaRebelloToledo]

Based on the Issue 7324, after implementing the DistributedCachePlugin class, when using the removeAccount method, the credentials were not cleared from my client cache. So, I started investigating and uploaded new personal versions of the library with logs during the entire account removal process and noticed that at the final moment of passing where the cache object was cleared, when trying to recover the KVStore cache, it was empty, that is, it was impossible to identify the partition key, preventing the clearance of the credentials in the client cache. However, I performed a validation where, if the accountEntities were empty, it would search for the partition key from my partition manager, correcting the problem of not clearing the credentials.

Previously, when using the removeAccount method, the accountEntities array was empty during the afterCacheAccess phase, preventing extraction of the partitionKey.

Now, if no accountEntities are available, the partitionKey is fetched from the partitionManager to ensure that the cache can still be updated.

• Refactored the afterCacheAccess method to check if accountEntities is empty.
• If accountEntities is empty, fetch partitionKey from partitionManager.

Before the fix:

After the fix:

Test results:

[LuccaRebelloToledo]

@microsoft-github-policy-service agree