-
Notifications
You must be signed in to change notification settings - Fork 3.3k
ClientAssertionCredential constructor fails if kwargs are provided #33673
Copy link
Copy link
Closed
Labels
Azure.IdentityClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Metadata
Metadata
Assignees
Labels
Azure.IdentityClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Type
Projects
Status
Done
Describe the bug
The ClientAssertionCredential constructor accepts the
authorityandadditionally_allowed_tenantsarguments through kwargs. However, if any of those arguments are provided, they are incorrectly bubbled up through a super().init(**kwargs) call toGetTokenMixinandabc.ABC. That ultimately makes construction fail with:To Reproduce
Expected behavior
The
ClientAssertionCredentialobject is built successfully.Additional context
I'm currently working around this by forcefully inspecting the credential object and injecting the settings as needed.