Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
platform
active.directory
adsi
adsi.iis-admin
base
com_ole
complus_mts
component_svcs
database
directx
gdi
graphics_mm
internet.client
internet.server
internet.server.isapi-dev
localization
mapi
messaging
msi
mslayerforunicode
multimedia
networking
networking.ipv6
sdk_install
security
shell
telephony.tapi_2
telephony.tapi_3
telephony.tsp
telephony.wte
tools
ui
ui_shell
win_base_svcs
win16
  
 
date: 19 May 2006 14:32:55 -0700,    group: microsoft.public.platformsdk.internet.server.isapi-dev        back       


Modifying ACLs for IISFilter key in the metabase   
Hello,
             I have created an ISAPI filter DLL and I am installing it
using a script. The portion that installs the filter is the standard js
which looks something like this:
     Note that the "siteFilters" is a filter node obtained previously
    // Add the filter
    var myFilter = siteFilters.Create ("IIsFilter", filterName);

    // Set the appropriate filter path
    WriteLine("Set filter path : " + filterPath);
    myFilter.FilterPath = filterPath;
    WriteLine("Filter path set successfully.");
    myFilter.SetInfo();

        The problem I am facing is that after this the filter gets
installed successfully and it works well too but when in the IIS
snap-in when I right-click the virtual directory and check the ISAPI
filter tab in the properties it shows priority field as "*Unknown*" and
the arrow also does not appear.
       Now when I change the ACL (using Metabase Explorer) of this node
so as to give the "filters" node "Write" permissions the UI shows the
appropriate priority and also the arrow.

      The question I have is that is there a programmatic way to change
the ACL of the "Filters" node or one of its children?

Thanks,
Suyog
date: 19 May 2006 14:32:55 -0700   author:   Suyog

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us