asked on Domain credentials not the same for SQL 2014
I had installed a querying program that uses the user's windows credentials to query the data. I went into SQL and added the user using Windows credentials. The user went into SQL is as mydomain\user. However, when I go into the querying tool security program and grant access it picks up the user as mydomain.com\user. So when the user tries to login the user ID's do not match. I am not sure if there is something that needs to be fixed in SQL or in active directory.
Windows OSWindows Server 2012SQL
Last Comment
rwheeler23
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
It has something to do with this application. I used the SQL AD browser to pull the user. The application has the same type of browser. The problem is that when the application pulled the user it added the '.com' suffix and then when it goes to encrypt the user's password it uses this version not the version without the suffix. So now when the user tries to login to the application the login fails because the combination of username and password do not match what is in SQL. I have asked the creator of this application how to proceed.
where is the failure the authentication in the SQL or a subsequent verification....
Look at sql auth events to see whether it is the one rejecting the ..
Commonly, when using windows integrated authentication in an application, there would not be a need to list/select the user, the user loged into the system is whose token the application provides to the sql server to access.
it sounds as though the application ......
the display commonly is domain\username the suffix is dropped. check the options on the application whether you can narrow down the user listing to use domain versus domain.suffix...
Look at sql auth events to see whether it is the one rejecting the ..
Commonly, when using windows integrated authentication in an application, there would not be a need to list/select the user, the user loged into the system is whose token the application provides to the sql server to access.
it sounds as though the application ......
the display commonly is domain\username the suffix is dropped. check the options on the application whether you can narrow down the user listing to use domain versus domain.suffix...
ASKER
Good idea. They have gone home for the weekend so I will check on Monday.
ASKER
It appears the issue is that this client is still using a W2000 server as the AD. No matter what we do the windows credentials will not work for this application. I am trying to convert to sql credentials.
ASKER
Thanks for your insight.