Windows Components

New Veridium Windows components implement client support for new functionalities and fixes for known issues:

Credential Provider:

• Fixed a bug that prevented local accounts to work correctly together with the Credential Provider.

• Fixed the “Tail” typo (corrected to “Tile”) in multiple strings across the product.

• Fixed an issue that prevented VFace to work correctly when access to temporary files was needed.

• Fixed an issue that caused a crash in BopsLogonService if UseSIDasDeviceCertCN=1 after an upgrade.

• Fixed an issue that caused a no-response situation if the user scanned the QR code in LogonUI and screensaver started before entering the next auth step.

• Improved the desktop fingerprint sensor (DactylID20) support

• Added support for LDAP password reset/renew via Veridium server feature.

• Support for QR code as a secondary authentication.

• Support for QR Offline in Journey is controlled by step in Journey.

• QR Offline will not be displayed if the credentials are not cached (i.e. when using RDP to a different domain).

• Support for QR Offline in ShellExtension by enabling the following registry keys for PIN rotation:
  UseOpenSSLForEncryption:DWORD=1

  IdentityFormat:STRING:=”sAMAccountName”

• Improved the support for users coming from different domains in ShellExtension.

• Introduced a new registry key “DistinguishUnlockLogon=DWORD:”, with the default value 0 (disabled). When this key is enabled, it will distinguish between unlock and logon Credential Provider scenarios and send then accordingly to the VeridiumID server. This will help in setting granular journey options for users.

• Fixed a bug that caused a crash in Credential Provider when debug registry key was enabled for users that did not have permissions to trace files.

• Improved the behavior in the scenario where multiple certificates are generated in the Personal certificate folder. If multiple certs are found, they will be cleared and a new one will be generated instead.

• Added indication of Credential Provider usage, so more granular journey configuration can be set for specific scenarios. using conditions in Orchestrator:
  

  

  CPUS_INVALID = 0, CPUS_LOGON = ( CPUS_INVALID + 1 ) , CPUS_UNLOCK_WORKSTATION = ( CPUS_LOGON + 1 ) , CPUS_CHANGE_PASSWORD = ( CPUS_UNLOCK_WORKSTATION + 1 ) , CPUS_CREDUI = ( CPUS_CHANGE_PASSWORD + 1 ) , CPUS_PLAP = ( CPUS_CREDUI + 1 )

RAEP:

• Fixed an issue that prevented installation on other partitions, except the default C: one.

Windows Credential Provider v.3.5.5 build 262: