Hello all,
We have an issue with our RDM.
I tried to find if there is a same issue already posted in forum, but couldn't find anything.
The issue which we are facing is that from time to time when we start our RDM we are getting prompted to configure again MFA for our data source.
Somehow the configuration is getting deleted/lost.
We are using Team RDM V. 2024.1.23.0 64-bit on VDI using FSLogix as profile manager.
Our data source is on Microsoft SQL Server.
Cheers,
Samir
Hi Samir,
Thank you for contacting us.
We had another client report this issue in the past, and we have been trying to identify the root cause for a while now. Improvements have been made in v2024.2 & v2024.3, so I would suggest you upgrade to the latest version and see if the issue persists for you.
If you still see the issue happening, we could enable tracking of the MFA settings in your database. This will allow us to debug the issue further.
Best regards,
Stéfane Lavergne
Hello Stéfane ,
Thx for the fast respond.
We will proceed with the upgrade.
This was also in prior version the issue, so we upgraded to the current one.
Do you maybe know where RDM saves MFA Configuration ?
Under appdata/local, or somewhere else ?
Cheers,
Samir
Stored in the UserSettings column of the [dbo].[UserAccount] table.
The value should look something like this:
<DataSourceUserSettings>
...
<TwoFactorInfo>
<AccountName>--some-name--</AccountName>
<AuthenticationType>GoogleAuthenticator</AuthenticationType>
<IsConfigured>true</IsConfigured>
<Key>--random-text--</Key>
</TwoFactorInfo>
...
</DataSourceUserSettings>
What we suspect is happening is that the UserSettings field is being reinitialized, causing the MFA configuration to be lost and prompting you to reconfigure a new MFA.
Stéfane Lavergne
Thx for the feedback.
We will then proceed with the upgrade and see how it goes.
Hopefully the issue will be gone :)
Will keep you in the loop in this post.
Cheers,
Samir
I will send you 2 SQL scripts via private message.
The first script, tr_UserAccount - TwoFactorInfo Saver.sql, will enable MFA history via the UserInfoHistory table. This could be useful in diagnosing the issue if it's still present.
The second script, tr_UserAccount - v5.820.sql, will revert the changes in case, for any reason, it causes issues in RDM. A fail-safe, if you will.
tr_UserAccount - TwoFactorInfo Saver.sql script.UserInfoHistory table, any changes made to the TwoFactorInfo (XML tag) within the UserSettings field of [dbo].[UserAccount] will be logged here.
Best regards,
Stéfane Lavergne
Thx
Will do