B
Bryan
I have a vb.net application that connects to Web Service
pages *.asmx running on a local instance of IIS. These
webservices connect to a SQL server on another machine.
The web services are set to impersonate user, and Windows
authentication. All is well.
Next, I moved the webservices to another server running
IIS, which happens to be the SAME machine as SQL server
that these services connect to. My app can connect to the
Web service pages, but the web service fails to propgate
the CLIENT user/login credentials to the SQL server, and
it uses the NT AUTHORITY\Anonymous account for some reason.
I can't figure it out, but I've heard mention of similar
issues being solved with modifications to
Machine.config... any ideas?
The point of this is that I want to use the SQL SUSER_SNAME
() functions to restrict/change the views in SQL, so that
function needs to return the username of the authenticated
client.
pages *.asmx running on a local instance of IIS. These
webservices connect to a SQL server on another machine.
The web services are set to impersonate user, and Windows
authentication. All is well.
Next, I moved the webservices to another server running
IIS, which happens to be the SAME machine as SQL server
that these services connect to. My app can connect to the
Web service pages, but the web service fails to propgate
the CLIENT user/login credentials to the SQL server, and
it uses the NT AUTHORITY\Anonymous account for some reason.
I can't figure it out, but I've heard mention of similar
issues being solved with modifications to
Machine.config... any ideas?
The point of this is that I want to use the SQL SUSER_SNAME
() functions to restrict/change the views in SQL, so that
function needs to return the username of the authenticated
client.