-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[msal-node][msal-common] Update generation of client info headers #1482
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-node][msal-common] Update generation of client info headers #1482
Conversation
@@ -1,30 +1,31 @@ | |||
{ |
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.
Only relevant change here is the addition of "resolveJsonModule": true. (I also fixed the indentation, and thus the big diff)
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.
Added some comments
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.
See comments, we should make the platform packages define client info header values.
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
Clean up imports in msal-common tests
…node-refresh-flow
…AzureAD/microsoft-authentication-library-for-js into sagonzal/msal-node-refresh-flow
[msal-node][msal-commmon] Add support for acquiring tokens with a refresh token to msal-node
…lt-headers [msal-node][msal-common] Update generation of client info headers
Moving the generation of the client info headers from msal-common into msal-node. If these values are not passed in from msal-node (or from whoever is calling into msal-common), then we fall back to generating them in common.
Client info headers: