MFA database connection broken in 2022.3.x.x

Hello,

Thank you for reporting this issue. We have recently found this problem and an internal ticket is already opened.

The problem is related to the Force 2FA parameter. The workaround for now would be to downgrade RDM to 2022.2.29.

Once a fix will be available, we will post it here.

Thank you for your patience.

Best regards,

thank you

Hello,

For your information, the issue has been resolved and the fix is available in the latest RDM version 2022.3.18.

Let us know if that works properly.

Best regards,

Hello Erica

Thank you. Since tomorrow is a holiday in our region, we won't push the update today.
I'll plan it for next week and keep you posted.

With kind regards,
Nick

Hello Nick,

Thank you for your feedback. We will then wait next week for the result of the upgrade.

Enjoy your holiday and long weekend!

Best regards,

Hello Erica

We just performed the upgrade ... and had to roll-back once again.

The issue is resolved on our Windows hosts, but Linux hosts are still affected.

I've created a new post on the Linux Forum.

With kind regards,
Nick

Hello Erica

We were now able to perform the upgrade on Linux reliably. This issue seems to be resolved on both platforms.

With kind regards,
Nick

Hello Nick,

Thank you for your feedback and that's a good news the issue is now solved on both platforms.

Best regards,

Hello Erica

We are running 2022.3.27.0 since a few days.
This week I started receiving notifications that our Windows user have to re-activate MFA when launching RDM.
Today, I also had this issue.


When looking at the data source settings, the MFA option is gone.


Basically, it's the same issue as previously mentioned in this thread.

I had this issue after a Windows update. It seems that a full shutdown of Windows (or full reboot) will trigger this.

With kind regards,
Nick

Hello Nick,

Could you please make sure the 2FA is properly set in System Settings as stated in this article?
https://kb.devolutions.net/rdm_enable_2fa_users_sql_server.html?q=mfa#force-application-security-with-totp-(authenticator)

Let me know if that helps.

Best regards,

Hello Erica

We've configured the MFA on the data source, not the application itself.

The enforcement on the data source is configured as mentioned in the article.


With kind regards,
Nick

Hello Nick,

Thank you for your feedback.

As the 2FA is now saved in the database and not in the data source anymore, could you please try to create a brand new data source in RDM? Please do not duplicate the current data source in File - Data Sources as I want you to create it from scratch.

Let me know if that help to fix the issue.

Best regards,

Hello Erica

I'm sorry for the late response due to the holidays.

It used to be that in this screen, you could configure the MFA-option.
(As the name suggest, I created a new one. Since I had to use the same database to have some entries, I could connect immediately with the already existing TOTP configuration.)

As one can see, it is gone.

It's unclear how to setup correctly, since one will receive an error when trying to connect the first time.
Furthermore, the fact that Windows update triggered a reconfiguration of the MFA seemed undesired.

Am I missing something?

With kind regards,
Nick

Hello Nick,

Since the 2022.3 release, the MFA is configured under My Account Settings > Data source MFA:



There were issues with the automatic migration of the MFA from locally to the database in earlier version of RDM, but those issues were fixed. In the 2022.3.28 version of RDM, there were also a fix for the "Force data source 2-factor configuration", in some cases it was prompting every time a new authentication to the data source was performed.

Best regards,

Hi Richard

Thank you. That explains the behaviour we were experiencing.

The best wishes for the new year!

With kind regards,
Nick