Ensure to only clear current client cache when logging out #1068
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
When calling
logout
, we would callcacheManager.clear()
without specifying any client id, resulting in clearing all data from the cache, including those belonging to other clientId's as the one configured in the current Auth0Client instance.When using local storage, this results in logging out both
app1.domain.com
andapp2.domain.com
(both using a different clientId), when that might not be intended.Unless the user sets
clientId
to null, we should only clear the data from the cache that belongs to either the providedclientId
, or the globally configuredclientId
.References
Fixes #1063
Testing
Checklist