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
RSA Access Manager integration with eRoom is not working. Number of Views RSA Authentication Agent for Web: IIS Authentication Test Fails Due to Node Secret Mismatch with RSA Authentication Manager Number of Views How to enable ISAPI filter in IIS 7.0 Number of Views Determine the correct root (base DN) and user search filter when configuring an identity source for the RSA SecurID Access… Number of Views How to Determine RSA Authentication Manager 8.x is using TLS 1.2 Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA SecurID Authentication Engine 3.0.0 for Java Release Notes How to Download OTP Token Seed Files from myRSA CyberArk Password Vault Web Access - RADIUS Configuration with Authentication Manager - RSA Ready Implementation Guide Importing an SSL console certificate PKCS#12 file to the RSA Authentication Manager 8.2 Operations Console fails with pass…
Don't see what you're looking for?
