Access Manager agent on IIS 6, plus Site Executive

Does anyone have experience using the Access Manager agent for IIS 6 along with Site Executive? I've got a user who has installed this on his web server and I'm trying to help him use AM to protect the server.

Site Executive installs an ISAPI filter, which seems to be intercepting requests before the agent gets them, and redirecting them to directories like /bin and /se. Since the AM agent is protecting the URLs that users type in (like /private-stuff or whatever), AM is not enforcing restrictions properly -- it's not configured to protect the URLs that eventually go through it.

And it's not as easy as simply configuring AM to protect the /bin and /se directories, since they're used by everything in the environment. That is, /public-site gets redirected there as well as /private-site. So I can't easily protect some directories but not others.

If anyone here has experience with Site Executive and AM, I'd very much like to hear from you. My user has version 3.5.5 of Site Executive installed.

[1036 byte] By [plt667] at [2007-11-26 8:45:03]
# 1

The IIS6 agent is a wildcard ISAPI filter. Is the Site Exclusive a wildcard ISAPI filter as well? If not then maybe IIS6 invokes the registered ISAPI filters before the wildcard ones in which case I don't think there is an easy solution. If memory serves correctly one cannot simply register the IIS6 agent as a normal ISAPI filter instead of a wildcard one.

Aaron_Anderson at 2007-7-6 22:28:30 > top of Java-index,Web & Directory Servers,Directory Servers...