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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: