Got this warning: You are still using the legacy security which will be removed soon...
I noticed today that we got this warning:
You are still using the legacy security which will be removed soon. Consider switching to the permission system instead of the security groups
If I go into Administration -> Security Groups (Legacy), I have no security groups
If I go into Administration -> System Settings -> Security Settings, the "Use legacy security" is checked (on)
So, can I just turn off "Use legacy security" because I have no security groups or do I need to look other places before turning off this setting?
Hello,
Sure you can turn this option off as you are not using any Security Groups.
For the other customers that are using Security Groups in Administration -> Security Groups (Legacy), it is important to set the permissions using the User Groups Based Access Control before disabling the Use Legacy Security option in Administration -> System Settings -> Security Settings.
Best regards,
Érica Poirier
Hello Anders,
Just a quick update to inform you that a ticket has been opened with our Engineering Department and they are currently working on this issue.
We will be in touch as soon as we will have an update to provide.
Best regards,
James Lafleur
@Erica, thank you for the confirmation.
@James, I don't think there is an issue, just a matter of confirming that I didn't do anything wrong.
Hello Anders,
Thank you for your swift reply!
I can confirm that you are not doing anything wrong. Since you are not using the "Security Groups" disabling this option is what we recommend.
As for my comment, it was meant to inform our community that we are currently experiencing an issue where users can receive this prompt even if the "Security Groups" are not in use. That being said, a ticket has been opened to have this fixed.
Sorry for the confusion.
Best regards,
James Lafleur
Hi James,
Thank you for the explanation. I thought the message was working as designed, because I had the setting turned on (but not using Security Groups). Makes sense not to show the message, if there is not action needed.
/Anders
We too are seeing this message, but we are in fact using Legacy Security Groups. The options presented in the linked document reference shared by Erica are not available to us through the Administration interface (specifically, I do not see User Groups under the Administration tab), so unfortunately we do not see a way to migrate away from the legacy model. Do you have a document that shows us how to move from the legacy security setup to the modern approach?
Hello FM Admin,
What type of Data Source are you currently using? Is it a Devolutions Online Database by any chance?
Best regards,
James Lafleur
Hi James,
Yes, it is an online database.
Thanks
Hello,
In that case, you are correct, the Devolutions Online Database only supports the Security Groups. That being said, since the Devolutions Online Database will be replaced by the Hub Business solution, you will have access to the User Groups.
Best regards,
James Lafleur
Hi James,
Thanks for the update. Do you know what the timeline is for that product replacement? I want to make sure we are ready for it.
Have a good evening!
Hello,
Thank you for your swift reply!
In order to prepare for that replacement, I would recommend consulting this link https://kb.devolutions.net/kb_online_database_dodb_eol_announcement.html
Best regards,
James Lafleur
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
Hello,
After having a discussion on that matter with our Engineering Department, they confirmed that this option will still be in RDM 2022.1, which means that it will stay available for another 6 months.
As for the second part of your reply, I would recommend opening a ticket through RDM by going under Help -> Submit a support ticket. We will be able to assist you and provide you with the information that you need to prepare for this change.
Best regards,
James Lafleur