Fixed claims not being updated by just using the token for the userId #125
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…laims from the userManager - Removed claim consolelog from testing
MertzAndreas
requested changes
Dec 6, 2024
- Made both policies asynchronous
LokeSGJ
approved these changes
Dec 6, 2024
MertzAndreas
approved these changes
Dec 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The token is now just used to get the userId, which is then used to get the user's claims via the userManager. This should fix the bug with tokens not being refreshed whenever a user joins an organization for example.
Removed claim consolelog from testing
Changed auth policies from singletons to Scoped
Related issues
Tokens not refreshing their claims when a user joins an organization for example
Checklist