CA Mobile OTP Desktop client 2.3.1 does not allow second device registry

Document ID : KB000099942
Last Modified Date : 02/06/2018
Show Technical Document Details
CA Mobile OTP client  is used for secure  access to a company's application. This  client runs on mobile phones as well as on desktops. This issue is related to registry of devices using the desktop client only. A user may encounter a issue registering their second device using the CA Mobile OTP Desktop client Version 2.3.1.  Certain browsers for example Chrome 42 and above exposed an issue with the CA Mobile OTP client version 2.3.1,
CA mobile OTP Client version 2.3.1 on a desktop 
The cause of this issue is "Un-populated required AOTPXML string in Arcot ARUDSUSER table" post a registration completion. When registering a new device the OTP Desktop version fails to update the ARUDSUSER table with the required AOTPXML string for proper and complete registration. Any operation on this incompletely registered device fails.

Please upgrade to version 2.3.3 of the OTP Desktop client. Find the new client bundled in CA Strong Authentication Version 9.0 related release bundle. is the software to download from for version 9.0