Unfortunately I don't think there's a lot of information on how this works.
I've looked for this for quite some time as well in the past and couldn't
get much. Microsoft is pretty tight lipped about the Worker Process, ISAPI
interfaces to ASP.NET etc. and label that as implementation specific.
As far as security goes, the worker process is started by using the account
you specify in the App Pool. You can check that in Task Manager which shows
the real account, rather than what's impersonated. So I'm not sure what you
mean by Ghost account...
ASP.NET can add impersonation ontop of the launching account depending on
the settings in web.config. If Impersonation is on, ASP.NET will run under a
different account than the underlying account the Worker process is running
under.
Maybe this will help:
http://west-wind.com/weblog/posts/2153.aspx
+++ Rick ---
--
Rick Strahl
West Wind Technologies
www.west-wind.com www.west-wind.com/weblog
"Studio P.M." <St******@discussions.microsoft.com> wrote in message
news:C2**********************************@microsof t.com...
Does anyone know a valid and compete reference paper about what the
"Worker Process" precisely is and does? So far I couldn't find any.
Reason is that during last weeks I had to go deep down into SharePoint
security, and the related identities. Which, by the way, as I realized,
are
at least two: the Log on "real" one, and the Application Pool "ghost" one;
under which, indeed, the "Worker Process" is said to operate: wherefrom
the
reason for this question.
Thanks for your attention.
P.M.