Incompatible signing algorithm for azure-keyvault
See original GitHub issueNot sure if this is the SDK’s issue but I’m getting this error:
Error: Key and signing algorithm are incompatible. Key <my-key> uses curve 'SECP256K1', and algorithm 'ES256K' can only be used with curve 'P-256K'.
My understanding is that SECP256K1 is P-256K.
https://docs.microsoft.com/en-us/azure/key-vault/about-keys-secrets-and-certificates
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Common error codes for Azure Key Vault | Microsoft Learn
VaultAlreadyExists, Your attempt to create a new key vault with the specified name has failed since the name is already in use. If...
Read more >azure.keyvault.keys.crypto package — Azure SDK for Python 2.0.0 ...
Verify a signature using the client's key. Requires the keys/verify permission. Parameters. algorithm ( SignatureAlgorithm ) – verification algorithm. digest ( ...
Read more >What to do when Azure Key Vault rejects certificate and says ...
Unsupported key operation(s): "wrapKey", "unwrapKey". Supported values are "sign", "verify". Does anyone know what to do about this? Of course I ...
Read more >AZIdentity | The Azure Key Vault ECC Certificate FAQ
But you need a self-signed ECC certificate for Apple Pay, ... "Elliptic Curve Cryptography Public Key Algorithm of the X509 certificate in ...
Read more >How to configure digital signing in Advanced Installer Azure ...
Automating digital signing process using Azure DevOps pipelines and Advanced Installer. ... By loading the certificate from Azure Key Vault.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I got it working using
ECDSA256
as the algo name, in the place ofES256K
. Just FYI.Looks like the issue has been fixed as the above user got it working. If the error persists feel free to re-open this issue in the azure-sdk-for-js repository.