Remove hard-coded loadUserInfo to make it configurable #2167
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.
Hello @dannyrb ,
I have removed the hard-coded
loadUserInfo: true,
when creating the UserManager. This flag causes an additional call to the userinfo endpoint as described in the oidc-client documents:With AzureAD this call can cause a 401 as described in this ticket: IdentityModel/oidc-client-js#1028
By hard-coding this to true, it is not possible to work around this issue. (If not configured this value is true by default anyway, which makes this even more useless)
Without this line of code it is now possible to disable the loadUserInfo and therefore make the oidc authentication with AzureAD work.
Example config: