Tom Mucha

FYI we do have a support ticket, but I wanted to start a conversation here. Ticket 00012262.

We were affected by the bug in the new version where MFA is enforced at the data source level, people could get in to change that MFA after upgrading, so many of us had to uninstall and reinstall the .2 version. Looks like .3 fixes that, but when the MFA screen pops up, all my MFA information is gone.

For one of our SQL data sources that we want to keep a little more secure, we're using Duo MFA enforced along with custom logins controlled through RDM versus standard SQL/AD creds. This lets me distribute the .rdd file, and then I have the users just edit it, change their user name in 3 spots, enter in their PW and DB passphrase, and we're good - all the MFA information for DUO in in that .rdd file.

My guess is that MFA is no long shared through the .rdd file? With the new .3 version, I imported an rdd file, and it didn't bring in the mfa info. I don't like the idea of distributing my Duo integration key and secret to users, and I think those have some kind of hash in the rdd file (please correct me if I'm wrong!). Is there a new way of centrally managing this for corporate deployments where we don't want users keying this information in?

Tom

I just updated RDM the other day and received this, had to come to the forum to find anything about it. I didn't even see anything about this in the release notes. Do you have any more details when legacy security will be removed? We've been on the same SQL DB since 2011 and we're now up to just north of 11,000 entries, so need some time to figure this out. I want to make sure my users don't update RDM and then they can't do anything.

On a side note (can open another post/reach out to support) any new tips in the past 10 years (time flies when you're having fun) for larger SQL RDM DBs? One of my other RDM DBs we setup was integrated with DUO and we used "Custom (Devolutions)" as the auth type and that seems to work well rather than dealing with SQL based auth.

Tom

This isn't really support related, just wanted to thank the team at Devolutions for something I just noticed after upgrading to 2020.2.12.0. I go between 2 data sources all day long, both MS SQL based. One data source is just over 10k entries, the other is tiny, around a hundred. When in online mode, switching to the larger data source would freeze up RDM and Windows for a few seconds. It's something we just dealt with and wrote off to the huge size. With this new version I'm not seeing any of that freezing happening switching between data sources. Thank you!!!!

Tom

Thanks Stefane - I updated this morning. At first, I was unable to check any boxes still. I was not able to select auto-assign or assign to individuals. Re-reading your post, I saw you said you registered a new license. I deleted the license and then re-added it - boom - I was able to select everything I needed.

Not sure if removing and adding the license back would have fixed it in the old versions, but at this point everything is working for me.

Thank you!

Tom

Thanks for the followup - I'll keep an eye out for updates and followup if there are any issues!

Tom

Sounds good! Basically the check boxes can't be selected in my case to either auto-assign or assign to individuals. I verified it is a site license in case there is some checking going on. If you need any other info let me know!

Tom

Hi Stefane - I just wanted to follow up on this. We're currently on 2019.2.22, do you know if it should be working in this version? I hate giving away our key for users who are performing fresh installs, the old method worked very well for keeping that hidden! We have a site license, and all the options under the license admin can't be selected.

Thanks!

Tom