Skip to content
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

[Implementation] Enhance MSAL Client-Side Telemetry #5130

Open
gladjohn opened this issue Feb 11, 2025 · 0 comments
Open

[Implementation] Enhance MSAL Client-Side Telemetry #5130

gladjohn opened this issue Feb 11, 2025 · 0 comments

Comments

@gladjohn
Copy link
Contributor

Task type

Development

Description

  • Add tracking for MSI source (IMDS, App Service, Service Fabric, AKS, IMDSv2, etc.).

Expose MSI source as a new telemetry field.

  • Capture Token Revocation Events for MSI V1

Log occurrences of bypass_cache=true when set.

  • Capture Token Revocation Events for MSI V2

Capture error_code responses from /credential endpoint.

  • Detect and Log Certificate Type Used for MSI Authentication

Track if platform certificates, developer-provided certificates, or in-memory self-signed certificates are used.
Ensure telemetry provides insights into bound token adoption.

  • Capture Failure Reasons for MSI Token Acquisition

Log and categorize token acquisition failures: Authentication failures, Network issues, HTTP 404 errors

Solution

No response

@gladjohn gladjohn added internal untriaged Do not delete. Needed for Automation confidential-client telemetry and removed untriaged Do not delete. Needed for Automation labels Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant