Open MatthewSteeples opened 7 months ago
Thank you for opening this issue, we will look into it.
Hi, I saw the same behaviour today when I was trying to list the secrets of a KeyVault.
az keyvault secret list --id /subscriptions/${subscriptionId}/resourceGroups/${resourceGroup}/providers/Microsoft.KeyVault/vaults/${keyVault}
This results in
ERROR: Bearer token authentication is not permitted for non-TLS protected (non-https) URLs.
I was running this command in an Azure DevOps pipeline after loggin in with a ServicePrincipal, but it also occured when executing the command locally and being authenticated with Azure.
Environment information
{
"azure-cli": "2.62.0",
"azure-cli-core": "2.62.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"aks-preview": "0.5.121",
"azure-devops": "0.26.0",
"bastion": "0.3.0",
"ssh": "2.0.2"
}
}
@rcomanne Please use az keyvault secret/certificate list
with --vault-name
as a workaround. The auth issue with --id
is under investigation.
I received the same error when running the following:
az keyvault role assignment create \
--role "Key Vault Administrator" \
--scope "/" \
--assignee "$OBJECT_ID" \
--name "$NAME" \
--id "/subscriptions/$SUBS/resourceGroups/$RG/Microsoft.KeyVault/vaults/$KV"
Also tried with --id "https://$KV.vault.azure.net"
, but got another error, this time HTTP 404:
<div id="content">
<div class="content-container"><fieldset>
<h2>404 - File or directory not found.</h2>
<h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>
</fieldset></div>
</div>
Hello,
Same issue here using the Windows version.
If we try from azure cloud shell it works.
Same issue here
Describe the bug
On Az CLI version 2.59: trying to list certificates using the Id of the KeyVault results in an error message
Related command
az keyvault certificate list --id /subscriptions/{SubScriptionId/resourceGroups/{resourceGroup}/providers/Microsoft.KeyVault/vaults/{vaultName}
Errors
Bearer token authentication is not permitted for non-TLS protected (non-https) URLs.
Issue script & Debug output
Expected behavior
Certificates to be output
Environment Summary
Additional context
az keyvault certificate list --vault-name {vaultName}
works fine on the same device