[FEATURE REQ] Make it possible to pass correlation id through ClientCertificateCredential to MsalConfidentialClient/AcquireTokenForClientParameterBuilder

[austvik]

Library name

Azure.Identity

Please describe the feature.

For tracability I want to add the correlation id to authentication calls which are done through the ClientCertificateCredential (I guess this is an issue for all the different credential classes).

The call is done through the MsalConfidentialClient, which internally uses the client to create a AcquireTokenForClientParameterBuilder.

This builder has a WithCorrelationId, but there is no way to signal to the MsalConfidentialClient through the ClientCertificateCredential that we want to add more parameters to the builder.

Please make it possible to add more parameters (like correlation id) to the authentication calls.

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[christothes]

Hi @austvik - Would wrapping your GetToken calls in HttpPipeline.CreateClientRequestIdScope address your issue?

[github-actions]

Hi @austvik. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[austvik]

I give the CertificateCredential to a Azure.Messaging.EventHubs.Primitives.PartitionReceiver which creates an Azure.Messaging.EventHubs.EventHubConnection with it. EventHubConnection has an InnerClient of type Azure.Messaging.EventHubs.Amqp.AmpqClient which, if it is missing a token, calls AcquireAccessTokenAsync which ends up calling GetTokenAsync.

I can try to wrap all calls to methods of the PartitionReceiver with HttpPipeline.CreateClientRequestIdScope

Thank you!