New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[msal-core] Fix response type configuration by basing it mainly on scopes #2022
Conversation
… are configured or clientId is the only scope
…eToken APIs as well as remove clientId as single scope restriction from msal-core.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall nice work! Just a few comments about cleaning things up a bit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few nitpick suggestions but looks good otherwise
…tId to avoid confusion in the future
…n and prevent it from returning true when the scopes array is empty
…oft-authentication-library-for-js into scopes-and-response-types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! A few nits
…oft-authentication-library-for-js into scopes-and-response-types
…oft-authentication-library-for-js into scopes-and-response-types
This PR:
openid
orprofile
openid
andprofile
to the request scopes by default if they are missingScopes
andResponse Types
behavior for msal-core