When you have more than 2 sub domains in Active Directory(AD) but only define the top level domain (for backend authentication) in IDENTIKEY Authentication Server(IAS), you get the error message "user not found" for the authentication.
When you are monitoring the IDENTIKEY Appliance with SNMP, the system description field isn’t updated after an upgrade from version 184.108.40.206 onwards. For example. When you do an upgrade from 220.127.116.11 to 18.104.22.168, the IDENTIKEY Appliance version that is acquired through SNMP remains 22.214.171.124
When running custom reports on IDENTIKEY Authentication Server 3.11 R2 you get the following error message: Error Code: ’(17)’ ; Message: ‘class vasco::IndexOutOfBoundsException: Error -1 in function “Iterator::operator* (Element does not exist)”: An unspecified error occurred’
When you are doing Offline Activation using CRONTO Technology through the User Self-Management Website you get the following error: MDL Registration Failed / Returncode: -1 / Status Code: -19
When configuring IDENTIKEY Authentication Server with Thales nShield HSM and using version 11.70 of the Thales client software, the IDENTIKEY configuration wizard fails with NCIPHER API ERROR: <56> : <ServerNotRunning>.
This article explains how to unwrap/decrypt a software-level transport key that is wrapped by a Key Encryption Key (KEK). Keywords: DPX, DPX-Key, KEK, HSM
After upgrading to DIGIPASS for Apps or DIGIPASS for Mobile version >= 4.10 (from a version <= 4.9.x) on iOS, it is not possible open the secure storage: A secureStorageSDKException is thrown with error code -4305 when calling SecureStorageSDK.initWithFileName:useFingerPrint:andIterationNumber.
When using the email function of the Message Delivery Component (MDC) to send Activation Data of a DIGIPASS for Mobile, the email with the activation code is sent, but the QR code is not attached.
With IDENTIKEY Authentication Server 3.10 with AD data store it’s impossible to create a DIGIPASS User Account when a user has performed a (failed) login in the past. The error “Failed to execute create” is returned.
The audit file size displayed in the Log File Management section of the configtool and size after the audit file has been downloaded do not match. This article explains why.