Skip to main content
Skip table of contents

AzureKeyVaultCryptoToken Algorithm Support

This page lists algorithms that are known to work or not work with the current implementation. Also, see the specific SignServer Signer for algorithms that signers can work with and review signer-specific algorithm support pages.

The following lists supported algorithms that are known to work with most workers and therefore the list may not be complete.

For algorithms supporting withECDSA, a signature algorithm matching the ECDSA curve must be specified in the SIGNATUREALGORITHM property. For example, use SHA384withECDSA for a key using secp384r1/P-384.

Signature Algorithms

 

Algorithm Name

Also Known As

Comment

(error)

SHA1withRSA

RSASSA-PKCS_v1.5 using SHA1

 

(tick)

SHA256withRSA

RSASSA-PKCS_v1.5 using SHA256

 

(tick)

SHA384withRSA

RSASSA-PKCS_v1.5 using SHA384

(tick)

SHA512withRSA

RSASSA-PKCS_v1.5 using SHA512

 

(error)

NONEwithRSA

RSASSA-PKCS_v1.5

 

(error)

SHA256withRSAandMGF1

RSASSA-PSS using SHA256

(error)

SHA384withRSAandMGF1

RSASSA-PSS using SHA384

(error)

SHA512withRSAandMGF1

RSASSA-PSS using SHA512

 

(error)

NONEwithRSAandMGF1

RSASSA-PSS

 

(warning)

SHA256withECDSA

ECDSA using SHA256

Azure Key Vault requires the Signature Algorithm to be specified. See warning above.

(warning)

SHA384withECDSA

ECDSA using SHA384

Azure Key Vault requires the Signature Algorithm to be specified. See warning above.

(warning)

SHA512withECDSA

ECDSA using SHA512

Azure Key Vault requires the Signature Algorithm to be specified. See warning above.

(error)

NONEwithECDSA

ECDSA

Key Algorithms

 

Algorithm Name

Key Specification

Comment

(tick)

RSA

  • 2048

  • 3072

  • 4096

(tick)

ECDSA

Named curves:

  • secp256r1 / prime256v1 / P-256

  • secp384r1 / P-384

  • secp521r1 / P-521

 

Add a comment

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.