mRemoteNG
mRemoteNG copied to clipboard
Change SQL Server support of mRemoteNG
Hi,
That's a feature request.
Currently, mRemoteNG allows to have connection configurations on a SQL Server. That's a great feature, but it lacks some things:
First, maybe the configuration from SQL Server should be in folder-level and not application level. For example, you can share some folder with your teammates via SQL Server and have all of us the same configurations, but allow too to have a "local" connections folder not stored on SQL (not shared connections).
Second, allow to have a "offline-copy" of the connections, or use SQL as a sync repository. With the actual situation of home-working, sometimes you cannot enter the SQL server but you need to use a connection. That's can be resolved if SQL are used as a sync repository (if you create a new connection offline, when SQL is reachable these connection will be uploaded. Also, if other people creates the connection, then your client download it).
That's can be related with #1949 comment of better SQL Server support. I think the AD intergration commented here would be wonderful, but not everytime you can rely on AD to enter computers (for example on my case I use lot of computers from my AD, but also lots of computers from outside).
this is planed to implement with a new branch and its belongs to profiles. In my plans is to add local SQLite file as well so we can store "offline" data but need to be sure we will do that secure way.
I will just add another needed SQL feature is that credential replacement would be nice. We team-share our RDP connections but for some servers we share logins and for other servers we have unique logins per user.
Another approach of looking at his may be split configuration, where the server name & IP is stored in SQL but the credentials to connect are stored on the local database
I am planning to make profiles - in profile settings you will be able select authorisation type (windows, sql, AD, Azure AD, email, etc,) and also select that to include from connections - that can be also selectable - load part from db, another part from profile etc. will be fully configurable so you may select that to use, but fully functional it will be in 1.8 version, for 1.7 I only planning to fix current issues and fix some major bugs we have
Hi, are there any news for the sql support? I'm trying to impement mremoteng for our team, where we share rdp connections, so i need a centralized db.
Hi, yes in new release config db will be provided so you could set access to SQL and then manage users acls on DB side (if you wish)
Hi, thanks and when will the new version be released?
just restored my account for GitHub (as lost my phone and cant overtake 2FA without) so will be working on to commit changes and do release of NB first the earlest