How to determine if RSA Access Manager IIS agent is deployed as an ISAPI filter or a MODULE?
Originally Published: 2013-11-21
Article Number
Applies To
Issue
The RSA Access Manager Agent for IIS can be deployed as either an ISAPI filter or as a Module. These are essentially different agents, although they share some common code they use many different methods. The agent log file does not clearly indicate which version of the agent is used.
Cause
Resolution
In the debug log file the <config> section with the copyright information does not tell you if a module or filter is being used, but in the <info> level logged at debug log level if the ISAPI filter is being used the text [httpFilterProc] will be displayed.
As an ISAPI filter
2013-11-21 11:11:49 -0800 - [3956] - <Info> - [HttpFilterProc] RSA Access Manager Agent 5.0 for IIS 7.0 initialized
As a Module
2013-11-21 12:47:18 -0800 - [1956] - <Info> - RSA Access Manager Agent 4.9 for IIS 7 initialized
Related Articles
Determine the correct root (base DN) and user search filter when configuring an identity source for the RSA SecurID Access… 134Number of Views Running script to determine if hardware appliance can successfully upgrade to Authentication Manager 8.7 SP1 435Number of Views Node secret mismatch when testing authentication of RSA Authentication Agent for Web: IIS with RSA Authentication Manager 479Number of Views How to enable ISAPI filter in IIS 7.0 1Number of Views RSA Access Manager integration with eRoom is not working. 14Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Installation Guide RSA Governance & Lifecycle 8.0.0 Administrators Guide
Don't see what you're looking for?