Interesting... thanks for the explanation.
I'm still curious about the technical explanation for this though. Why
would a STA COM object not have access to the impersonation token if
it's created in ASP.NET without aspcompat=true?
Wouldn't this also imply that in addition to bad performance and
2002 8:42 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Impersonation, COM and ASP.NET
To answer my own question here, for the archives:
Set the aspcompat=true in the @page directive seems to fix the problem.
I'm going to assume that creating the STA component in the ASP.NET MTA
somehow ca
To answer my own question here, for the archives:
Set the aspcompat=true in the @page directive seems to fix the problem.
I'm going to assume that creating the STA component in the ASP.NET MTA
somehow caused it to lose the impersonation token. I'd be interested in
a more detailed explanation as
Hi,
I'm wondering if someone could shed some light on what seems to be very
unusual behaviour with ASP.NET. This has been driving me nuts for
days...
I've setup windows authentication and impersonation in my web.config
file. I'm using Keith Brown's utility [1] to confirm that impersonation
is
