Set IS_USER_RESOLVED property when ValidateUsername is enabled from adaptive script #231
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 the Identifier First, when the
ValidateUsername
is configured as authenticator config, the user is resolved and theisUserResolved
flag is correctly set in the authentication context. However, when ValidateUsername is set via an adaptive authentication script parameter, the user is still resolved, but isUserResolved is not set in the context.This PR ensures that
isUserResolved
is correctly set in the context even when ValidateUsername is enabled through the adaptive authentication script.Refer: