June 25, 2015 at 1:50 pm
Instructions for Application software installation, (at a point where it connects to SQL Server) from vendor state: "to use Windows Authentication, also add the domain; for example: user@domain.com"
When I try to connect as "user@domain.com" I get a message in the SQL Error log: "Login failed for user 'user@domain.com". Reason: Could not find a login matching the name provided."
When I try to connect as DOMAIN\user, I get: "Login failed for user 'DOMAIN\user'. Reason: Attempting to use an NT account name with SQL Server Authentication"
The software will make a SQL Server Authentication connection unless the login name is in the form "user@domain.com"
If I create a login in SQL Server in the form of "user@domain.com", SQL Server renames it DOMAIN\user.
Anyone see how I could navigate around this roadblock??
June 25, 2015 at 1:57 pm
Since this is vendor supplied software, I'd ask them for clarification. But it sounds like you should have an account in SQL Server Domain\User, then users logging into the app will use the format user@domain.com and the application will 'convert' it to Domain\User to connect to SQL Server.
We have several applications which work that way...you log into them using one account and they access SQL Server using another account.
-SQLBill
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply