--- title: "Authentication Suite Server SDK for HSM Version 4.0.2 (July 2026)" slug: "a3s-hsm-release-notes-4-0-2" updated: 2026-11-11T09:52:07Z published: 2026-11-11T09:52:07Z canonical: "docs.onespan.com/a3s-hsm-release-notes-4-0-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Authentication Suite Server SDK for HSM Version 4.0.2 (July 2026) > 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 FIDO2 device binding support The Vision FX provisioning protocol is used for authenticators that combine Cronto visual cryptography with FIDO2 hardware-bound credentials, such as DIGIPASS FX2. As such, it incorporates the FIDO2 protocol for user authentication and the Cronto protocol for transaction data signing. Authentication Suite Server SDK now supports FIDO2 device binding and provides the following new APIs for integration with HSM: - `AAL2GenGenMessageActivation1Cmd()` - `AAL2ProcGenMessageActivation1Rpl()` - `AAL2GenVerifyDeviceCodeExCmd()` Corresponding wrapper functions are also available for Java and .NET. Retrieve BLOB encryption algorithm The new non-HSM `AAL2GetBlobInfo()` function allows you to retrieve information about the algorithm used to encrypt the authenticator BLOB data. .NET wrapper compatibility enhanced The .NET wrapper has been updated to .NET Standard 2.0, providing the following compatibility improvements: - Compatibility with applications built on .NET (up to version 10) - Compatibility with applications built on .NET Framework (up to version 4.8.1) - Improved cross-platform compatibility ## Deprecated components and features Supported platforms and other third-party products This version no longer supports the following products: Hardware security modules - Thales ProtectServer 2 - Thales ProtectServer ## Known issues 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