Minimum Permission to run ISAPI Filter under IIS 6.0

I was wondering if there are any articles regarding the permissions that are
required to run ISAPI filter in II6.0 with regular domain user as "Identity"

Basically, what kind of ACL (system resources) I need to be able to load
ISAPI Filter under domain user context.

I can't load the isapi no problem if I add this domain user to local admin
group, which I don't want to. So has anyone setup isapi in this scenario
before???

Thanks

The only permission necessary to run ISAPI Filter on IIS6 is allowing
IIS_WPG (i.e. the AppPool Identity) read access to the DLL. Anything else
is completely dependent on the permissions required by the particular ISAPI
Filter.

Thus, if you ACL the ISAPI Filter DLL to allow IIS_WPG read access, IIS6
should load it. Whether the ISAPI Filter has sufficient privileges running
as the AppPool Process Identity, that is up to the design of the particular
ISAPI Filter.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"winzin" <winzin.DeleteThis@discussions.microsoft.com> wrote in message
news:D731DB20-96B9-40CB-A0D6-99AE2F883278@microsoft.com...
I was wondering if there are any articles regarding the permissions that are
required to run ISAPI filter in II6.0 with regular domain user as "Identity"

Basically, what kind of ACL (system resources) I need to be able to load
ISAPI Filter under domain user context.

I can't load the isapi no problem if I add this domain user to local admin
group, which I don't want to. So has anyone setup isapi in this scenario
before???

Thanks