|Applies To||RSA Access Manager 4.9 Agent for IIS7 / 7.5|
|Issue||AxM - 4.9 Agent for IIS7 module prority and order|
What is the explanation of modules priority setting (cleartrust.agent.iis.priority=HIGH) and order in module list?
When the module loads, we register our priority (default High) with IIS for the callbacks/events we are interested in such as OnPostAuthenticateRequest. Our module gets executed before modules that have registered at a lower level. If multiple modules hooking the same event have registered at the same level then it is the order in the module list that determines who is called first.
|Notes||RSA Agent for IIS7 is now an http module and no longer an isapi filter as in previous versions 4.8, 4.7, 4.6|
By default we install at the bottom of the module list. One of the reasons to list our module at the end is to make IWA work. For IWA to work our module should be placed after the WindowsAuthentication module. There may be more dependencies.
|Legacy Article ID||a55620|