Dynamic discovery provider locator can't resolved principal #5988
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
|
Thank you. Have you already run the style guide on this change? |
|
I think i fix it. |
|
merged via 2e142fe799a81e5ea890d1b17350a327d19c047a |
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.
Hi,
We use Dynamic Discovery Provider, to determine Client to authentication ( We have Office365 and soon OpenAM). We have about 150 auth request per minute. When I try upgrade library from 6.5 to 7.0 there is a problem to determine where forward client.
I found that in class DefaultDelegatedAuthenticationDynamicDiscoveryProviderLocator was added Principal Resolver. Default Principal Resolver is EchoingPrincipalResolver called from ChainingPrincipalResolver, where EchoingPrincipalResolver always return NullPrincipal.
Result: It cannot find Client to redirect.