[BUG] Enabling VisualStudioCodeCredential on macOS crashes dotnet #14362
Comments
|
Thank you for your feedback. Tagging and routing to the team member best able to assist. |
|
Hi @bawoodruff , do you have this issue with Azure.Identity 1.2.1 as well? |
|
@AlexanderSher Yes, just updated to 1.2.1 and have the same issue. My workaround is to Exclude this for now on non-Windows but would prefer to not special case this. |
|
Have the same issue on OSX. Application crashed with exit code 11. |
|
@Igor-Pchelko What version of OSX do you have? |
after disabling VisualStudio / VSCode credentials it works on OSX: builder.AddAzureKeyVault(new Uri("https://test.vault.azure.net/"), new DefaultAzureCredential(
new DefaultAzureCredentialOptions
{
ExcludeVisualStudioCredential = true,
ExcludeVisualStudioCodeCredential = true
})); |
So do you also have an exception in this combination: new DefaultAzureCredentialOptions
{
ExcludeVisualStudioCredential = false,
ExcludeVisualStudioCodeCredential = true
} |
|
In my case, my sample code was reduced to the only condition required to cause the exception: VisualStudioCodeCredential |
|
@bawoodruff , you are right the culprit is |
|
Looks like I have test that reproduces the issue, now has to figure out how to fix it. |
Thanks this helped me to resolve connectivity issue. |
|
Why is this bug closed? This workaround breaks on Windows, it feels a bit crispy to add this to every project: |
Yes, this doesn't seem like a satisfactory solution to this issue at all. |
|
Definitely still an issue - this should not be closed |
|
I tried to reproduce this with the following package versions on .NET 5 and am unable to reproduce. This is with the latest version of VSCode and utilizing the VisualStudioCodeCredential to authorize to Azure.
|
|
Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you! |
|
I was able to fix it by upgrading to latest version of Azure.Identity in .Net Core 3.1 |
|
Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you! |
|
I see similar issue on @azure/identity npm package. I am using the latest version 2.0.1. |
Describe the bug
Since 1.2.0-preview2 (introduction of VIsualStudioCodeCredential), dotnet will crash when attempting to access a keyvault secret.
Microsoft.Identity.Client.Extensions.TraceSource Error: 0 : [MSAL.Extension][2020-08-19T02:32:50.9087760Z] SecKeychainFindGenericPassword, for serviceName Microsoft.Developer.IdentityService and accountName MSALCache
Status: '-25300'
Failed, item not found
Expected behavior
No crash.
Actual behavior (include Exception or Stack Trace)
dotnet crashes, report from console... and then Apple Problem Report...
To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)
Environment:
Azure.Identity 1.2.0-preview2 or later
.NET Core SDK (reflecting any global.json):
Version: 3.1.401
Commit: 39d17847db
Runtime Environment:
OS Name: Mac OS X
OS Version: 10.15
OS Platform: Darwin
RID: osx.10.15-x64
Base Path: /usr/local/share/dotnet/sdk/3.1.401/
Host (useful for support):
Version: 3.1.7
Commit: fcfdef8d6b
.NET Core SDKs installed:
3.1.301 [/usr/local/share/dotnet/sdk]
3.1.401 [/usr/local/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.7 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.7 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.7 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.7 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.7 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
The text was updated successfully, but these errors were encountered: