Allow for extension / customization of AzureIdentityAccessTokenProvider::GetTokenAsync

[MattKotsenas]

The problem

I have a multi-tenant app, and as a result need to generate per-tenant tokens. However, I'm not able to set the tenantId parameter in the GetTokenAsync call here:

kiota-dotnet/src/authentication/azure/AzureIdentityAccessTokenProvider.cs

Line 117 in e2dfd84

var result = await _credential.GetTokenAsync(new TokenRequestContext(scopes, claims: decodedClaim, isCaeEnabled: _isCaeEnabled), cancellationToken).ConfigureAwait(false);

As a result, I need to duplicate the entire implementation of AzureIdentityAccessTokenProvider to set that one value.

The request

My request is to update / refactor AzureIdentityAccessTokenProvider to allow for inheritance / extension of this type of scenario (there are other parameters that others might also want to set such as isProofOfPossessionEnabled and proofOfPossessionNonce) by moving the actual GetTokenAsync call into a virtual method.

[baywet]

Hi @MattKotsenas
Thank you for using kiota and for reaching out.

Is there any specific reason why you're not setting the tenant id on the credential object instead?

[MattKotsenas]

Hi @baywet!

I'm in a multi-tenant app scenario where I'm using a ChainedTokenCredential and iterating over many tenants, including tenants that can be provided dynamically.

As such, rather than creating an ever-growing list of credentials, I'm setting up the credential with the common tenant and then passing tenant as part of this token call.

Let me know if that helps, or if I've misunderstood the question. Thanks!

[baywet]

Thank you for the additional information.

This is the first time we're getting such a request. I believe one way we could achieve that is by having the access token provider and the authentication provider constructors accept a token request context factory (essentially a callback).
What do you think?