-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: handle case where account entities is empty in after cache access #7329
fix: handle case where account entities is empty in after cache access #7329
Conversation
@microsoft-github-policy-service agree |
@LuccaRebelloToledo This fix will require a new unit test in DistributedCachePlugin.spec.ts. |
@Robbie-Microsoft At this point I'm in doubt about how to run the unit test because I found that in TokenCache.spec.ts the data is not fully mocked and actually uses the TokenCache functions. Should I change to use it like in TokenCache.spec.ts or should I continue mocking the functions and results? |
…ing cache state consistency post-serialization
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Result of tests in DistributedCachePlugin.spec.ts
Thanks so much for highlighting this issue and proposing a fix @LuccaRebelloToledo |
@LuccaRebelloToledo, you've done a fantastic job with that unit test + improvements to the testing constants. Thank you! We can get this merged in to our dev branch after this passes the CI pipeline, which I've enabled for this PR. |
You will need to run the "beachball" command in the root of the repo. See more info in our contributing doc. |
Thank you so much Robbie, this means a lot to me!! I'll remove the empty line and run the "beachball" process right now. Thanks again! |
Merged in #7426 |
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.
Before the fix:
After the fix:
Test results: