Skip to content
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

Security improvement by moving away from "DefaultAzureCredential" #280

Open
doormalena opened this issue Oct 18, 2024 · 0 comments
Open

Comments

@doormalena
Copy link

The following is written on https://learn.microsoft.com/en-gb/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet stating that "DefaultAzureCredential" is not to be used in production scenarios.

Simplifies authentication while developing apps that deploy to Azure by combining credentials used in Azure hosting environments with credentials used in local development. In production, it's better to use something else. See [Usage guidance for DefaultAzureCredential](https://aka.ms/azsdk/net/identity/credential-chains#usage-guidance-for-defaultazurecredential).

Consider allowing the user of AzureSignTool to specify which credential is to be used via a new additional parameter related to --azure-key-vault-managed-identity. For example, my needs would be the "WorkloadIdentityCredential". For others, this could be InteractiveBrowserCredential or anything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant