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

[Feature Request] Expose requestID or correlation ID for requests made to AAD #494

Closed
pranavgk opened this issue Aug 25, 2020 · 3 comments
Closed
Assignees
Labels
enhancement New feature or request fixed
Milestone

Comments

@pranavgk
Copy link

Is your feature request related to a problem? Please describe.
Currently, we want to investigate an issue with the token received as part of the OBO flow. Since we don't have a request id or correlation id, we are having trouble in identifying the logs of the calls made for obtaining the token when we call await tokenAcquisition.GetAccessTokenForUserAsync(scopes);

Describe the solution you'd like
A request ID or correlation ID that we could trace back the requests for AAD in Kusto would go a long way in achieving traceability.

Describe alternatives you've considered
Any other solution that lets us trace the AAD calls would work too.

Additional context
N/A

@pranavgk pranavgk added the enhancement New feature or request label Aug 25, 2020
@jmprieur jmprieur added this to the 0.3.1-preview milestone Aug 25, 2020
@jmprieur
Copy link
Collaborator

Blocked as ASP.NET Core seems to not provide the x-ms-* headers which contain the correlation ID.

@jmprieur
Copy link
Collaborator

@jennyf19 assigning this to you.
I think that for our partners it's important to have it for GA, along with the extra query parameters

@jennyf19 jennyf19 added this to the GA version milestone Sep 30, 2020
@jennyf19
Copy link
Collaborator

included in 1.0.0 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fixed
Projects
None yet
Development

No branches or pull requests

3 participants