0

My plan is the following:

  • Add logon name to SQL database.
  • Save service account username and password to SQL database against each of these users, as a hash.
  • User opens up app on their PC, it reads their logon name, checks if the service account credentials are there, if they are, pull them down and use them to authenticate against the domain network.
  • If the users' logon name isn't there, throw an error.

Is this possible? If so, does anyone know how to translate the hash for Windows Authentication?

Steve Ayers
  • 86
  • 8
  • Don't know if my post was unclear, but I'm getting the user to authenticate against the network with a different account, so no. The service account may have different domain permissions etc which we don't want deployed to other users. – Steve Ayers Nov 13 '15 at 11:11
  • Steve I think your question would be better suitable for http://dba.stackexchange.com/help/on-topic –  Nov 13 '15 at 11:32
  • I don't think so, as the main thing I need to find out is how to convert a password hash so I can use for windows authentication....? – Steve Ayers Nov 13 '15 at 11:44
  • do you know the hashing algorithm? i doubt it... https://www.google.co.uk/?q=how%20to%20encrypt%20hash%20passwords –  Nov 13 '15 at 11:54
  • As a possible strategy, you could try writing a stored procedure using C# that ties to the windows API for authentication. – HashPsi Nov 13 '15 at 13:07
  • HashPsi, are you able to expand on that slightly? – Steve Ayers Nov 13 '15 at 14:21
  • You can't specify a password on logon when using windows authentication. Just use windows authentication as login-method in SQL-Server and make sure, server and client are in the same Domain or in trusted domains. – CPMunich Nov 13 '15 at 14:49

0 Answers0