Skip to main content
Skip table of contents

Plain Signer Algorithm Support

The following lists algorithm support for the Plain Signer.

The signer also relies on support for the algorithm in the Crypto Token used, so also review that the desired algorithm is supported by the configured crypto token. 

The following lists supported algorithms that are tested and known to work with a Crypto Token supporting it and therefore the list may not be complete.

Signature Algorithms


Algorithm NameAlso Known AsComment
(tick)SHA1withRSARSASSA-PKCS1_v1.5 using SHA1
(tick)SHA256withRSARSASSA-PKCS1_v1.5 using SHA256
(tick)SHA384withRSARSASSA-PKCS1_v1.5 using SHA384
(tick)SHA512withRSARSASSA-PKCS1_v1.5 using SHA512
(tick)NONEwithRSARSASSA-PKCS1_v1.5See Client-Side Hashing as special encoding of the request might be needed unless client-side hashing is specified explicitly in request metadata.
(tick)

SHA1withRSAandMGF1

RSASSA-PSS using SHA1
(tick)

SHA256withRSAandMGF1

RSASSA-PSS using SHA256
(tick)

SHA384withRSAandMGF1

RSASSA-PSS using SHA384
(tick)SHA512withRSAandMGF1RSASSA-PSS using SHA512
(tick)NONEwithRSAandMGF1RSASSA-PSSSee Client-Side Hashing as request metadata might be needed with the request.
(tick)

SHA1withECDSA

ECDSA using SHA1
(tick)

SHA256withECDSA

ECDSA using SHA256
(tick)

SHA384withECDSA

ECDSA using SHA384
(tick)SHA512withECDSAECDSA using SHA512
(tick)NONEwithECDSAECDSASee Client-Side Hashing for what the input should be.
(tick)Ed25519Pure EdDSA with Edwards25519
(tick)Ed448Pure EdDSA with Edwards448

Digest Algorithms Supported with Explicit Client-Side Hashing


Algorithm NameComment
(tick)SHA1
(tick)SHA256
(tick)SHA384
(tick)SHA512
JavaScript errors detected

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

If this problem persists, please contact our support.