I've used SQL authentication and windows authentication in my connection strings to SQL server just fine. I've got a login form that the user has to put their username/password in and it verifies to AD to ensure that is who it is and then logs in. Currently it is set to windows authentication.
I don't want to use SQL authentication because when the user changes their password from Windows the connection will still work.
My question is, what if a user tries to log into my application from a pc who's currently logged in user does not have access to the sql database? My guess is the AD verification will pass but when it tries to create a connection to the SQL server it will fail because the logged in windows user doesn't have access.
Is there a way to some how create a connection string to a SQL server that has the AD information in it as well so that it can authenticate using that? ...instead of trusted?