We are trying to create our device registration function for the CA Mobile OTP (ArcotOTP-OATH) and we are using the simulator program "arcot OTPDesktop" to test the registration.
We have prepared the provisioning URL, User ID and activation code as following:
1) Provisioning URL=http://{Server IP + Port}/arcotafm/controller_aotp.jsp?profile=mobileotp
2) User Identifier=user name of the user profile
3) Activation Code=OTP generated for such user
We can successfully register the 1st device, then we use the same value of (1) and (2), with a NEW generated OTP for such user at (3) to register the second device. But it return "Account Provision Error" and registration failed.
Is there anything wrong in our steps and what should be the valid scenario?
Here are the solutions to the roaming scenarios being faced by the customer:-
1) If 'CA mobile OTP Desktop Client' is used in end-user environment, we suggest them to use only IE to provision for first time but they can use any browser to provision later to other devices during roaming.
2) Alternately, end-user can use non-browser based Desktop OTP Client solution.