Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: Paolo F Cantoni on January 22, 2016, 07:06:19 pm
-
For reasons that might make your hair curl, I need to connect to the work SQL Server repository from my home machine.
I can (and must) connect to the work VPN to access the repository (even from a work machine on the work network - DON'T ask).
The VPN is active and works.
Obviously, the Windows authentication has the credentials for my home network and I need to establish the ODBC driver to use my Work credentials. Is there any way to do it?
I tried disabling Windows authentication on the connection dialog and "synthesised" the work credentials in the specific user area. But that doesn't help.
Does anyone know how I can accomplish this? Do I need to qualify the server name also? I guess I want to simulate the work me within a home me login.
Oh, nearly forgot. The bureaucratic effort required to implement the cloud access mechanisms (unless I can do it on my home machine) make that option unviable at present.
TIA,
Paolo
-
Hi Paolo,
If you're using some common "ea_dbuser" credentials to access the underlying database (which you enter in the ODBC connection dialog), then disabling Windows authentication and setting a password should work. EA should then prompt you for a user name and password when you connect.
However, if you're using your own credentials to access the database I'm pretty sure there's nothing you can do to get EA, or ODBC, to achieve this. At least I hope not -- it'd be a pretty massive security hole.
What you need then is some way to get your home machine to be accepted as part of the office domain. Here's a step-by-step approach (http://blog.lan-tech.ca/2012/07/25/how-to-join-a-windows-domain-using-a-vpn/) that I didn't write and haven't tested.
As an alternative, you could use Remote Desktop to open a connection to your office PC, log onto that in the normal fashion and run EA on it with the desktop remoted to your home PC. Provided, of course, that RDP is allowed over the VPN, and that your office PC is set up to allow RDP connections.
HTH,
/Uffe
-
Thanks Uffe for your input.
Unfortunately, the solution requires privileges I don't (and bureaucratically won't) have.
I DO RDP into my desktop from Home, but the desktop doesn't have the software required (my home machine does - hence why I need to connect) and (again) the bureaucracy makes it very difficult to get it on.
In the mean time, I've had an idea about an alternative solution, to the original problem, so "I'll give that a whirl".
Paolo
-
You should be able to specify a different username in the ODBC connection. You'll to preface the username with the Windows domain name. The quickest way to work out what to use is to open a command prompt on your work machine and run "whoami".