I logged on as administrator and created a trusted connection for a software that connects to my sqlserver. Then I logged on as a regular user and checked on the db server the users connected. Surprise: the user logged on was the administrator (the one that configured the connection) and not the current log-on user. Is it a "trusted connection" feature? I suspect that this behavior is introduced by my software. thanks in advance Agostino
I would check the application initiating the connection has not got a hard coded database username/password that it is using to connect
Basically, you are telling the application to impersonate the current logged on user's identity when connecting to SQL Server, instead of using a specific identity (username/password) in the connection string
If you need to pass a specific username/password then use
Now, to test for problems, try
Note: The username/password (or TRUSTED USER) must have the correct permissions on SQL Server.