Workspace not syncing between Devolutions_Hub/Authenticator_App Entries and the Authenticator

A fix for this issue has been implemented in version 2026.1.0
Backlog

Workspace not syncing between Devolutions_Hub/Authenticator_App Entries and the Authenticator

avatar

Hello there,

I noticed a few days ago that when creating a new OTP Entry, via RMD, that this Entry does not sync to the Workspace Authenticator, a few weeks ago this worked fine.

Currently 19 OTP Entries exist inside the "Authenticator App" Folder, but Workspace Authenticator only shows 13 Entries.

Meaning a new entry is synced TO the Hub but not the other way around.

I have a Devolutions Hub Personal connected with the App and sync/backup options are enabled.
Re-Login and Reinstall was already done.


Help would be greatly appreciated.

Best Regards

All Comments (3)

avatar

Hello,

Thank you for your message.

Starting with version 2026.1.1, the Authenticator section will be removed. All OTP entries will instead be accessible in a new dedicated section called OTPs inside your datasource. This change should resolve the synchronization issue you're currently experiencing.
If you have any further questions or need assistance after the update, feel free to reach out.

Best regards,

Dany Galarneau

avatar
Hello,

Thank you for your message.

Starting with version 2026.1.1, the Authenticator section will be removed. All OTP entries will instead be accessible in a new dedicated section called OTPs inside your datasource. This change should resolve the synchronization issue you're currently experiencing.
If you have any further questions or need assistance after the update, feel free to reach out.

Best regards,


@Dany Galarneau

Hi,

Thanks for the quick answer.

That's definitely helpful and good to know.
I guess version 2026.1.1 will not take long before release, so I will practice myself in patience.

Best Regards

avatar

Hello,

Thank you for being so patient!

I'm pleased to inform you that a new version of Workspace (2026.1.0) has been released, including this bug's fix.

Please let us know if this works or if you encounter any issues.

Best regards,

Dany Galarneau

A fix for this issue has been implemented in version 2026.1.0