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.

Sign up for GitHub

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

doc: add more context about DefaultAzureCredential Class #287

Merged
merged 2 commits into from
Dec 3, 2024
Merged

doc: add more context about DefaultAzureCredential Class #287

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
98d66d4
doc: add more context about DefaultAzureCredential Class
nicoklaus Nov 28, 2024
3e8b980
doc: improve wording
nicoklaus Dec 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,9 +96,7 @@ The single-file downloads do not require .NET to be installed on the system at a
Azure.

* `--azure-key-vault-managed-identity` [short: `-kvm`, required: possibly]: Use the ambiant Managed Identity to authenticate to Azure. This
can be used instead of the `--azure-key-vault-accesstoken`, `--azure-key-vault-client-id` and `--azure-key-vault-client-secret` options. This is useful
if AzureSignTool is being used on a VM/service/CLI that is configured for managed identities to
Azure. Important to mention is that this option leverages the [DefaultAzureCredential](https://learn.microsoft.com/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet) class which is trying to get a token via multiple options including Visual Studio Credentials and Interactive Browser Authentication.
can be used instead of the `--azure-key-vault-accesstoken`, `--azure-key-vault-client-id` and `--azure-key-vault-client-secret` options. This option uses a combination of authentication mechanisms listed under [DefaultAzureCredential Class](https://learn.microsoft.com/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet#definition). Beside Managed Identity, this also allows you to use existing sessions in the Azure CLI or PowerShell. It also supports Visual Studio Credentials, Interactive Browser Authentication and others.

* `--description` [short: `-d`, required: no]: A description of the signed content. This parameter serves the same purpose
as the `/d` option in the Windows SDK `signtool`. If this parameter is not supplied, the signature will not contain a
Expand Down