Simpler Description of Problem

[stevefromoz]

I have a second thread that is being passed the context from the main thread.
The functions that run within this thread start off by executing under the
(passed in) context but after completing the first few functions, the
remainder execute under the context of the App Pool identity.

All functions are in a single class/object.
There is no explicit call to drop/clear the context being used.
This happens only on one 2003 server.
I have reviewed a SQL trace and AS trace (the two services being called from
the functions) to prove that the 'true' identity is being used for the SQL
calls and that the App Pool identity is being used for the AS calls.

Again, would appreciate any input on how/why this could be happening.

Steve.

 

[Brian]

Hi Steve,

I don't know if this helps or not but I had threading problems that were
solved when I change aspnet.config as per:

http://www.leastprivilege.com/WhatIsAspnetconfig.aspx

Brian

 

[stevefromoz]

Hey Brian,

Thanks for this. I need to check the other servers settings tomorrow but
based on the server i checked tonight i don't think this is the issue.

The server i've checked so far had the default settings in place (ie ASP.net
isn't meant to allow the flowing of credentials across to the new thread) but
still flowed the credentials as per my code (very similar to yours as
described in earlier posts).

This other server (yet to check it's aspnet.config) is exhibitng strange
behaviour. The new thread is started and the main function is called. This
simply calls functions A and B, within the same class. When calling
functions A and B, all work performed in function A is done using the
impersonated account yet all work performed in function B is performed using
the App Pool identity acct. What i don't understand is why (or how?) should
or could the impersonation 'turn off' after the first function is completed.
I'm somewhat stumped...

Cheers,

Steve.

 

[stevefromoz]

Hey Brian,

Just wanted to post to say thanks, I logged on to my other server today,
made the aspnet.config change and voila, it all now just works. It's not
clear why it wasn't exhibiting similar symptoms on my other server(s) but for
now, i can live wihtout knowing why.

Thanks again,

Steve.