MS SQL Server Remote Management Session Type not working as expected
MS SQL Server Remote Management Session Type not working as expected
The recently added MS SQL Server Remote Management session (RDM 2025.2.x versions) doesn't seem to work correctly when trying to use user vault credentials.
When I create a new session in the following configurations, the session does not work as expected
Scenario 1:
- Credentials: "Username and password"
- Host: Server's FQDN
- Login Mode: "Integrated Security (Active Directory)"
- Result: Session opens as the same user running RDM, with no database or management access.
Scenario 2:
- Credentials: "Find by name (user vault)"
- Host: Server's FQDN
- Login Mode: "Database login" (this is the default, and it is greyed out unless "Username and password" is selected like in Scenario 1)
- Result: Login attempt uses username from the user vault, but doesn't recognize it as an Active Directory login, so the login fails.
Scenario 3 (Desired configuration):
- Credentials: "Find by name (user vault)"
- Host: Server's FQDN
- Login Mode: "Integrated Security (Active Directory)" (I tried setting this before changing the other drop-down off of "Username and password")
- Result: Logged in as the same user running RDM, with no database or management access. It doesn't use the user vault credentials at all.
We're running RDM 2025.2.14.0 on Windows, attached to Devolutions Server 2025.2.2.0. Is there any way to get this session type to use Active Directory Authentication with the user vault credentials?
Thank you!
All Comments (10)
Hello @zhopkins ,
Thank you for reporting these issues, I have logged a ticket and we will fix all these issues asap.
Regards,
Paul
Hello @zhopkins ,
Thank you for reporting these issues, I have logged a ticket and we will fix all these issues asap.
Regards,
Paul
@Paul Dumais
Thanks, we appreciate it!
@Paul Dumais Just circling back around. Any chance you all might have an ETA for this to be fixed? Thank you!
@Paul Dumais Just circling back around. Any chance you all might have an ETA for this to be fixed? Thank you!
@zhopkins
I am currently working on a solution as we speak, I'm very close to a solution. A lot of these issues are simply UI related things we need to clean up and make clearer. In order to authenticate as a different Windows User, that is a bit more difficult, you will notice that even SSMS doesn't let you select a different user than the one logged into windows (or if you do RunAs). That is because the default Microsoft SQL Server database driver only supports connecting with the currently authenticated windows user token. But we are working on a solution to this which should let you authenticated as any SQL Server user or Windows User.
Paul
Hi,
Any news regarding this issue ?
I have the same requirement: be able to authenticate with a windows user (not the user running the launcher) to a MSSQL instance.
Rgds
/Christian
Hi,
Any news regarding this issue ?
I have the same requirement: be able to authenticate with a windows user (not the user running the launcher) to a MSSQL instance.
Rgds
/Christian
@Cri25
Hello Christian,
We are working on a solution, it's quite complexe as the standard Microsoft SQL Server library does not support windows authentication as a different user (this is why SSMS requires RunAs). But we think we have a method to use our rust sspi-rs library as an authentication provider inside the Microsoft SQLClient library, but we are still working on this solution. We will let you know once we have working solution.
Thanks for your patience,
Paul
We've got the same issue (with our users working remotely on non-domain machines, connecting via Devolutions Gateway to our SQL servers). I know we could create SQL accounts for each user in each SQL instance, but that would be a bit of maintenance nightmare, so having domain user credentials working would be great!
We've got the same issue (with our users working remotely on non-domain machines, connecting via Devolutions Gateway to our SQL servers). I know we could create SQL accounts for each user in each SQL instance, but that would be a bit of maintenance nightmare, so having domain user credentials working would be great!
@stephencourtney1
Thanks Stephen, this is high on our priority list and we are working on a solution to allow authenticating to SQL Server with any Windows accounts without the need to "Run As".
Hi Paul,
I'm guessing this won't make it into the 2016.1 release, given that the Beta is already out, - any chance of it being in 2026.2?
Thanks!
Hello Stephen,
This is very high on my priority list, we are hoping to get to it as soon as possible. When I have a fix I will also try to back port it to a build as well.
Paul