Right now I am having the classic 'double hop' issue using windows
authentication and account impersonation. One machine is running the
report server (serv1) and contains half of the data we want to query.
The other machine, serv2, also contains a sql database, and the other
half of the data. I can run a report (using reporting services) on
serv1, and it is able to access serv2, serve up the report fine, etc.
When I run it on a client machine, I get an access error since the
serv1 machine is not able to pass credentials over to Serv2.
Now,
from what I understand about windows authentication, when serv1 gets a
request, it is able to determine the client credentials but itself runs
in a different context (nt authority/network service). Is there any
way I can tell Serv2 to recognize this account and give it read only
access? So the request goes from the client to serv1, and when serv1
accesses Serv2 it accesses it as t ...
Go to the complete details ...