MFA database connection broken in 2022.3.x.x

Hello Nick,

I opened a ticket for this issue with a high priority.

Regards,

Thank you.

Hi Nick,

A fix for this issue will be included in the next release.

Hello

Thank you, what is the ETA for the release?

With kind regards,
Nick

Hi Nick,

The build is currently in the testing phase. If everything is ok, It shouldn't be too long before we release the new version. Probably during the week, I'll keep you updated.

Thank you.

Hi Nick,

The new version 2022.3.0.6 has just been published. Quicker than I thought.

Hello Simon

Thank you. We will plan the upgrade as soon as possible. I keep you posted.

With kind regards,
Nick

Hello

We were able to perform the upgrade today.
Unfortunately, most Linux users reported that they had to change their TOTP. Is this behavior expected?

With kind regards,
Nick

Hello,

Just to confirm, by changing their TOTP, you mean setting it up again?

Best Regards,

Yes, exactly.

Hi Nick,

If the setting under "System Settings" -> "Security Settings" -> "Force data source 2-factor configuration" is enabled, a user will be forced to set a 2FA if he doesn't have one configured. If he already has one configured, he shouldn't be asked to change his 2FA. I will try to reproduce the issue. It only happened once to me.

Hello

All users have already set-up the MFA. All our Linux users had to "change" it the first time they connected to the data source after the upgrade.

With kind regards.

Does it continue to happen after the first time they connect to the data source? If so, It is an issue. If it only happens the first time after the upgrade, I will verify if this is expected.

Hello Simon

It happens every time.


With kind regards,
Nick

Thank you for the additional information. I opened a ticket and started working on it

Thank you.

I hope there is a fix soon, we receive quite a lot of complaints of the affected users.

With kind regards,
Nick

Hi Nick,

In the meantime, the window asking you to configure your MFA should prompt around three times when you press "Cancel". Maybe if you press cancel, it will find the correct MFA configuration the second or third time it shows. I cannot test this right now as I can't reproduce the issue repeatedly.

Hi Simon

I tried the bottom cancel button first. After three times it says it has no licence.

Then I restarted RDM and tried the top cancel button. That had the same effect. After 3 times it says no licence.


With kind regards,
Nick

Hello Simon

Are there any updates regarding this matter?

Our linux users are getting grumpy and upset.
Disabling the multi-factor authentication doesn't solve the issue.

With kind regards,
Nick

Hi Nick,

I've found a way to reproduce the issue on my end, and I may have an idea of what the issue is. Now that I'm able to reproduce it, it'll be easier for me to work on it.

Do you have MacOS users? If so, does this issue seem to happen on mac also?

Disabling "System Settings" -> "Security Settings" -> "Force data source 2-factor configuration" should let a user access the data source without a MFA configured. I'm not sure if It is what you mean by disabling the multi-factor?

Hello

To my knowledge, we don't have any Mac users, but I can get my hands on a Mac for testing if that is needed.

Yes, the setting that you described is what I did. It was still triggering the prompt to configure MFA.

With kind regards,
Nick

No need to find a Mac, I've just found something. These issues don't happen with the most recent version that we use internally. I'll find the changes that fixed these issues and add them for the next update.

Great, thank you!

I hope that the update arrives soon!

With kind regards,
Nick

Hi Nick,

I've found what was causing trouble with the MFA and made a fix. The new version (2022.3.0.8) will be ready to be tested soon. Some other issues related to the MFA were found, but from what I've seen, it shouldn't prevent linux users from using RDM.

The next update should fix these two issues:

• The MFA does not save correctly after configuration.
• The Prompt still triggers when the MFA is not mandatory.

Hopefully, this will relieve the frustration of linux users.

Hello Simon

Thank you. Any idea to what the ETA of the update will be?

Can you post an update when the update was released?

Thank you.

With kind regards,
Nick

Hi Nick,

The build will be tested soon today (it only contains this fix, should be quick) and will be released after that.

I will post here once the update is available.

The update is now available. Let me know if any other problems are preventing users from using RDM. Users should expect to have to configure their MFA after the update.

Good morning Simon,

Thank you, the issue is resolved.

With kind regards,
Nick