1

I have a vendor supplied application that I have very limited access to change. The application controls a machine, and cannot easily be logged off between users (expect up to 5 user changes per hour). I also have to deal with Part 11, and Corporate rules.

The plan is to have a shared login to the PC (AD user), then the application which has to connect to a MS SQL database anyways, will prompt for the user name and password, which it will use for the database connection. (previous user's DB connection will be closed between users). If the user/password does not authenticate, they will not be able to use the application.

I have AD authentication working, and I can connect with Server Management Studio using either a SQL user, or an AD user. The application can also connect using a SQL user. But the application always fails to connect when I attempt to use an AD user (I am only substituting the user/password, I have also tried to prepend the "Domain\" to the user). The application is using the default MS SQL drivers that are loaded when Server Management Studio is installed.

Is this even workable?

  • If you're attempting to enter creds then this will not work as SQL will see them a SQL credentials rather than Windows (so AD auth won't happen). The application would have to support that authentication method in order to use it, which it sounds like it does not. – Nic Apr 6 '17 at 16:42
0

Having an application connect would be very different than an end user on SSMS. Applications tend to use connection strings. Your applications connection string or config might need to be modified to connect to the SQL Server as an AD user as opposed to putting in a username/password for a SQL user.

You will want that user to have the same rights as the SQL User and probably want it to own the database. Contacting the vendor might be a good case. Going with AD users gives you more auditing visibility anyways which should please auditors.

Some connection string examples: https://www.connectionstrings.com/sql-server-2012/

  • 1
    That was great! It turns out that SQL authentication to AD only requires "Trusted_Connection=yes;" to be added into the connection string. (Assuming that AD authentication has already been configured on the DB. – Blaine Apr 6 '17 at 20:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.