Enable updating client assertions via callback #319
Merged
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
chlowell
requested review from
rayluo,
jhendrixMSFT,
bgavrilMS,
siddhijain and
keegan-caruso
rayluo
approved these changes
Jun 15, 2022
bgavrilMS
reviewed
Jun 15, 2022
bgavrilMS
reviewed
Jun 15, 2022
|
Kudos, SonarCloud Quality Gate passed!
|
keegan-caruso
approved these changes
Jun 24, 2022
bgavrilMS
reviewed
Jun 28, 2022
Merged
8 tasks
2 tasks
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.
This closes #292 by replacing the static string assertion with a callback that enables applications to generate assertions as needed. Following up on #313 (comment), I also removed assertion caching;
Credentialwill now acquire or create a new assertion for each token request.