You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed with E&D team following changed to be made to the telemetry client logging:
Api id to identify the type of request for example OBO/ Client credential
Type of confidential client for example if it is SNI based auth/ Certificate/ Assertion/ Managed Identity.
Log data for each resource in the scopes list.
Error codes: STS error code or MsalException error code (for client errors) or Exception type in the ErrorCode field.
Log token type as an enum instead of pop token.
Log the endpoint
Log the type of cache used. L1/ L2. This data can be stored in the TokenSource field. To make this change we need to expose a variable in TokenCacheNotificationArgs and pass this data back from Microsoft.Identity.Web.
In case of L2 cache failure (not cache miss, but for example timeout etc.), we want this logged as well. Perhaps a special TokenSource? (consider tracking separately)
As discussed with E&D team following changed to be made to the telemetry client logging:
Api id to identify the type of request for example OBO/ Client credential
Type of confidential client for example if it is SNI based auth/ Certificate/ Assertion/ Managed Identity.
Log data for each resource in the scopes list.
Error codes: STS error code or MsalException error code (for client errors) or Exception type in the ErrorCode field.
Log token type as an enum instead of pop token.
Log the endpoint
Log the type of cache used. L1/ L2. This data can be stored in the TokenSource field. To make this change we need to expose a variable in TokenCacheNotificationArgs and pass this data back from Microsoft.Identity.Web.
In case of L2 cache failure (not cache miss, but for example timeout etc.), we want this logged as well. Perhaps a special TokenSource? (consider tracking separately)
The details are listed in this document.
The text was updated successfully, but these errors were encountered: