As of version 4.0, OneSpan Authentication Server Framework has been renamed to Authentication Suite Server SDK for HSM. If not explicitly stated otherwise, any information and references to OneSpan Authentication Server Framework or VACMAN Controller also apply to Authentication Suite Server SDK for HSM.
New features and enhancements
Entrust nShield 5c/5s HSM support
This version provides support of Entrust nShield 5c and nShield 5s HSMs for Linux 64-bit and Windows 64-bit platforms using A3S C library, .NET, and java wrappers. It includes a new version of the Key Management Tool (5.0) compliant with Entrust FIPS-140 Level3 HSM mode.
Thales Luna HSM support
This version provides support of Thales Luna HSM for Linux 64 and Windows 64 platforms using A3S C library. Note that Thales doesn't provide an SDK to communicate with Thales Luna from .NET or Java applications at the moment.
Deprecated components and features
PDF documentation
The PDF documentation has been completely removed from the Authentication Suite Server SDK product deliverable. You can view the Authentication Server Suite SDK documentation exclusively online on the OneSpan documentation portal, available at https://docs.onespan.com/secsdks/docs/authentication-suite-server-sdk.
Supported platforms and other third-party products
This version no longer supports the following products:
Hardware security modules
Entrust nShield Connect
Entrust nShield Connect+
Entrust nShield Solo
Entrust nShield Solo+
Known issues
Authentication Suite Server SDK for Thales ProtectServer HSM
Usage restriction with the Thales ProtectServer2 HSMs in case of FIPS security mode enabled:
If the FIPS Algorithm Only flag is enabled on ProtectServer2 HSMs, the following restrictions will apply with the Authentication Suite Server SDK for Thales ProtectServer HSM:
Usage of HSM transport keys being double-length 3DES keys (DES2) is not possible.
Usage of HSM storage keys being double-length 3DES keys (DES2) is not possible.
Usage of HSM transport keys and HSM storage keys being triple-length 3DES keys (DES3) is not recommended in case of FIPS security mode enabled. For PSE2, as of the release PTK 5.6 / FW 5.03.00 in FIPS mode, DES3 keys can be only used a limited number of times before becoming inactive. It is strongly recommended to use AES HSM transport keys and AES HSM storage keys when the FIPS security mode is enabled.
Usage of DIGIPASS using a DES or 3DES algorithm is not possible.
Usage restriction with the Thales ProtectServer HSMs in case of FIPS security mode enabled:
If the FIPS Algorithm Only flag is enabled on ProtectServer HSMs, the following restriction will apply with the Authentication Suite Server SDK for Thales ProtectServer HSM:
Usage of DIGIPASS using a DES or 3DES algorithm is not possible.
Authentication Suite Server SDK for Entrust nShield HSM
Usage restrictions with multi-host configurations with Entrust nShield 5:
The OneSpan SEE machine for nShield 5 works with SEEJobs. The current version of Codesafe 5, however, only support SEEJobs to be called from a single host. A multi-host configuration is therefore currently incompatible with Authentication Suite Server SDK. This issue is planned to be resolved in a future version of CodeSafe 5 (currently scheduled for the first quarter of 2026).
Usage restriction with the Entrust nShield XC HSMs in case of FIPS 140-2 Level 3 Security World:
In case of FIPS 140-2 Level 3 Security World, the following restrictions will apply when generating keys with the manager-xc tool and with the nShield XC HSMs:
Generation of HSM storage keys being double-length 3DES keys (DES2) is not possible.
Generation of key encrypting keys being double-length 3DES keys (DES2) is not possible.
Generation of HSM transport keys being double-length 3DES keys (DES2) is not possible.
Usage restriction with FIPS 140-2 Level 3 Security World created as of nCipher security world software 12.50:
Since the version 12.50 of the nCipher Software and Firmware, the new security worlds which are created as from this version in strict FIPS 140-2 level 3 mode no longer alow the usage of the 3DES operations with the nShield HSM.
To possibly use 3DES HSM transport keys or 3DES HSM storage keys with the Authentication Suite Server SDK for Entrust nShield HSM, customers must either:
Use a security world (whatever FIPS 140-2 level 2 or FIPS 140-2 level 3) that was created prior the nCipher security world software 12.50
Use mandatorily a security world FIPS 140-2 level 2 if it is created as from the nCipher security world software 12.50
Limited performance with the Entrust nShield XC Base HSM:
The symmetric cryptography performances of the nShield XC Base when executed from a SEE machine are very low compared to the former nShield HSM devices based on the former PowerPCSXF architecture (nShield Connect/Connect+/Solo/Solo+). As a result the performances of the Authentication Suite Server SDK for Entrust nShield HSM when using a nShield XC Base HSM are significantly lower than when using a former nShield HSM.
Compared to usage with a former nShield HSM (nShield Connect/Connect+/Solo/Solo+), the performances of Authentication Suite Server SDK for Entrust nShield HSM are:
Around 5 to 6 times slower when using a nShield XC Base performance level
Almost similar when using a nShield XC Mid performance level
Around 2 to 3 times faster when using a nShield XC High performance level