I'm not sure that I've understood your application architecture correctly.
Could you please confirm which of the following is in use:
(1) browser -> web app -> web service -> SQL Server
OR
(2) browser -> web app -> SQL Server
If it's #1, are both the web app and web service configured to use
impersonation? If not, which is the one that is using impersonation?
Hi Nicole,
It's #1 and both web app and web service are using impersonation.
Nicole Calinoiu a écrit :
> I'm not sure that I've understood your application architecture correctly.
> Could you please confirm which of the following is in use:
[quoted text clipped - 47 lines]
> >
> > Eric
Nicole Calinoiu - 24 Oct 2005 15:32 GMT
Your central problem is almost certainly a credentials double-hop issue,
with the caller credentials from either the web app and/or the web service
not being useable downstream at either the web service and/or the database.
If you're unfamiliar with the double-hop problem, you might want to take a
look at http://msdn.microsoft.com/msdnmag/issues/05/09/SecurityBriefs/ for
an introduction to the double hop issue and how to deal with it. For a more
in-depth treatment of your various options for addressing the flow of caller
identity across the tiers of your web application, see
http://msdn.microsoft.com/library/en-us/dnnetsec/html/secnetlpMSDN.asp.
If you've already tried to address the double-hop problem by configuring
delegation, have you verified the user context in the web service and
database in order to confirm that it is flowing through as expected?
Hi Nicole,
It's #1 and both web app and web service are using impersonation.
Nicole Calinoiu a écrit :
> I'm not sure that I've understood your application architecture correctly.
> Could you please confirm which of the following is in use:
[quoted text clipped - 47 lines]
> >
> > Eric