How to determine if RSA Access Manager IIS agent is deployed as an ISAPI filter or a MODULE?
Originally Published: 2013-11-21
Last Modified: 2023-10-06
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
How to determine if MQBridge is configured and working in RSA Web Threat Detection 5.1 Number of Views Determining if the RSA Authentication Manager 8.x install platform is hardware or virtual Number of Views How to use the ASR to determine if 100% CPU Usage, Out of Memory Issues, and Periodic System Unresponsiveness are caused b… Number of Views How to determine the RSA Authentication Manager 8.x hardware platform Number of Views Password Available External email incorrectly defaults to localhost for hostname in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
