Use value instead of key for user-flows. #24443
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
ZhuXiaoBing-cn
requested review from
backwind1233,
chenrujun,
michaelqi793,
moarychan,
saragluna,
stliu,
yiliuTo and
zhichengliu12581
as code owners
ghost
added
the
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.
In aad b2c, map is used to store the type and name of the user flow in b2c, where the key stores the type and the value stores the name. In the access token, the name of the user flow will be used as part of the
iss, and the key stored in the key is currently used, which will cause problems. Here we will use value to solve the problem.