-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Instrument account type #7049
Instrument account type #7049
Conversation
): "AAD" | "MSA" | "B2C" | undefined { | ||
const idTokenClaims = account?.idTokenClaims; | ||
if (idTokenClaims?.tfp || idTokenClaims?.acr) { | ||
return "B2C"; |
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.
Do we ever expect this condition to be hit when collecting telemetry? AFAIK no 1P apps are using B2C
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.
We do not expect this condition to be hit for 1P apps. However, i would prefer to handle this scenario for 3P apps injecting custom performance clients.
4e68c33
to
414a24f
Compare
414a24f
to
b440b08
Compare
NOTE Account type is instrumented before (if exists) and after network/cache call to make it defined for failed requests when no response is returned.