HOWEVER if both web and application server are on the same machine make sure you edit your web.config file with. ![]() This does loose the granularity of individual Authentication as you are using a single account. To take care of this issue you can use impersonation and specify a username and password. The client will be authenticated with the webserver but those same credentials will NOT be trasfered onto the SQL Server if it is running on a different machine. If you are using Integrated Windows Authentication AND your database server and web server are on two different servers you will run into the double hop issue while authenticating. ![]() I'll assume this is a web application, if not sorry. ![]() Beware of the Windows Authentication double hop issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |