Good morning everyone,
I'm experiencing an anomaly related to being able to use the same instance of Google Authenticator on multiple devices.
Until recently, I was using the same 2FA code to access Remote Desktop Manager Free from two different PCs. What I did was export the configuration from Computer A and then import it into Computer B, also flagging the "Include data source credentials" option during export. This way it has always worked.
A few weeks ago I had to restore the operating system on Computer B and therefore I did the same operation. However, in this case, after having imported the configuration previously exported from Computer A, the system requests the TOTP code but signals "Invalid Code". Am I doing something wrong, or has something changed procedurally?
On both systems I'm using the 2022.3.23.0 64-bit version of Remote Desktop Manager Free.
Thanks so much for the support.
Sincerely.
Robert
Hello,
I would have to test the behavior on my side in order to see if I can reproduce it. Just to confirm, if you initially set up the 2FA on computer B, and import the configuration on computer A, do you have the same behavior?
Or if you set up a new 2FA on computer B, does it work properly?
Best Regards,
Etienne Lord
Good morning,
I apologize for the delay in replying.
In relation to what has been indicated, I would have some fear of importing from Computer B to Computer A as the latter is a critical system and I would not like the configuration to be altered in some way, making it unusable.
As for the "Independent" configuration of 2FA on Computer B, I confirm that it works correctly (but in this case, I should have two instances on Google Authenticator that actually refer to the same Data Source).
Thanks again for the support.
Hello,
Thank you for your reply,
My apologies for the delay, I'd like to make sure I understand your scenario the Authenticator is configured on the instance of RDM itself under "File" -> "Options" -> "Security" and you've moved it from one installation to the other by importing the remotedesktopmanager.cfg file is that correct?
Or is this a "One Time Password" entry that you've migrated from one installation to the other by following:
https://kb.devolutions.net/rdm_data_migration.html
I would also like you to confirm that the time on both workstations is the same, this could be the cause of your issue in this case.
Let me know,
Best regards,
Samuel Dery
Good morning,
thanks for replying.
Yes, the scenario is the first described. I generated a file called remotedesktopmanager.cfg by exporting the configuration with the "Include data source credentials" checkbox enabled. That same file was imported on the second Computer, but the Google Authenticator instance running on Computer A (from which it is the configuration was exported) does not work on Computer B (where it was imported).
As for date and time, they are exactly the same on both systems.
Thanks again.
Sincerely.
Hello,
Thank you for your patience,
I've performed a quick test on my end using a single workstation and I've been able to move the .cfg file from one installation to the other without encountering any problem with the 2FA code.
I'm wondering if instead of importing the "RemoteDesktopManager.cfg" file you manually move it to the new installation of RDM do you encounter the same issue? To do so simply copy the "RemoteDesktopManager.cfg" file from %LocalAppData%\Devolutions\RemoteDesktopManager on the original workstation and move it to the same location on the second computer.
You will need to make sure RDM is closed while performing this,
Let me know,
Best regards,
Samuel Dery
Good morning,
I finally found the solution to the problem. After trying everything, including what you suggested which is copying the config file instead of importing.
In practice, although the clocks of the two PCs in question were perfectly synchronized ("Set time automatically" activated and time synchronization also performed manually on both PCs), on the second system activating the "Set time zone automatically" option resolved the the problem. The clocks were still synchronized, but only by activating the above option (obviously active in the source system but not active in the destination system) is it now possible to use a single instance of Google Authenticator for both PCs.
Thanks a lot for your support.
Sincerely.
Roberto