Devolutions ForumDevolutions Forum

Different Domain Authentication

Different Domain Authentication

avatar
Bill Frisbee

I am a consultant using Remote Desktop Manager. I have my own RDM license and I use it extensively. My laptop is on a different domain (there is no trust). I have an Active Directory account on the client's domain and that account should have permission to connect to their RDM SQL database.

Is there a way to add their data source to my current RDM installation so I can switch between mine and theirs? I've tried to run another instance with runas and /netonly but it still shows me as being in my domain and not the target domain. For reasons I do not think they would want to create a SQL server account.

Is this doable?

Thank you.

To say can't is to fail before you begin

All Comments (4)

avatar
David Hervieux

Hello,
I will verify with one of our expert SQL Server expert. I'm not sure if we can impersonate a user in SQL Server.

Regards

David Hervieux

avatar
Maurice Côté

I will intervene just in case I get lucky.

I remember when I wrote the help topic below, I was surprised that SSMS showed my local username rather than the remote, and I has discovered that you had to run a query to get the identity from the server itself "e.g. SELECT SUSER_NAME()"

Manual RunAs - Devolutions Documentation (two screenshots at the bottom)

You say that "but it still shows me as being in my domain and not the target domain.", it could be the same problem that I had. How did you confirm that you were running under the local identity?

Maurice

avatar
Bill Frisbee
I will intervene just in case I get lucky.

I remember when I wrote the help topic below, I was surprised that SSMS showed my local username rather than the remote, and I has discovered that you had to run a query to get the identity from the server itself "e.g. SELECT SUSER_NAME()"

Manual RunAs - Devolutions Documentation (two screenshots at the bottom)

You say that "but it still shows me as being in my domain and not the target domain.", it could be the same problem that I had. How did you confirm that you were running under the local identity?


I was able to do the "RunAs" and pointed it to cmd instead of RDM. Running the command "whoami" told me my user context. My first thought was to use RDM to launch another RDM instance in the proper context (netonly is cool) but it did not cooperate. Then I tried a command line, then powershell. No joy.

To say can't is to fail before you begin

avatar
Stéfane Lavergne

RunAs is tricky, but I think this could work...

For RunAs /NetOnly to work you must be configured integrated security so with that in mind.

  1. Configure your data source with Login mode = Database Login, use your DB credentials
  2. Configure the client data source to be Login mode = Integrated security (Active Directory)
  3. Start RDM with RunAs /NetOnly using the clients domain creds


Both data sources should work in this scenario.

Please let me know if this helps.

Best regards,

Stéfane Lavergne