-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
WorkloadIdentityCredential: TypeError: Cannot read property 'tenantId' of undefined #25827
Comments
Proposed fix: |
Same bug for us, waiting for the PR to be resolved |
Same here, looking forward to fixing |
Same here. Is this a new issue? I am seeing this from today morning. |
Yes, this was added with the last release which added default credentials when using the DefaultAzureCredential constructor. All the credentials methods handle the fact that the "options" parameter is not mandatory and can therefore be "undefined" except for one which does not control this and causes the instantiation of DefaultAzureCredential to crash.
|
The PR by @orgads has been merged. I am working on releasing the fix in version 3.2.1. Will update the thread when it's out. |
Folks the version 3.2.1 for @azure/identity has released with the fix. Please feel free to use it. Also let me know if that works for you. Also thanks @orgads |
Hi @brianpham93. 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. |
On our side, the fix have corrected the problem. |
Thanks. The fix works for me |
Thank you so much for the confirmation. I'll go ahead and mark this issue as resolved. |
Describe the bug
If
DefaultAzureCredential
is used, this error will throw because there's noAZURE_TENANT_ID
in environment variablesTo Reproduce
Steps to reproduce the behavior:
Expected behavior
It should fallback to next available authentication option
The text was updated successfully, but these errors were encountered: