Release Notes › Web Agent Release Notes › Defects Fixed › Defects Fixed in 6.x QMR 1 › Conflict for the Web Agent with WebSphere and ServletExec 5.0 on the Same Web Server (29623)
Conflict for the Web Agent with WebSphere and ServletExec 5.0 on the Same Web Server (29623)
Symptom:
The IIS 6.0 Web Agent does not protect requests handled by WebSphere 5.0 or ServletExec 5.0 plug-ins installed on the same Web server.
Solution:
This is no longer a problem, but there are some restrictions regarding this issue.
The IIS 6.0 Web Agent consists of an ISAPI filter and an ISAPI extension. The majority of Web Agent processing occurs in the extension, following Microsoft IIS development guidelines.
These guidelines specify that for the IIS 6.0 Web server, the ISAPI filters should be used for filtering requests and the ISAPI extensions should be used to process and/or redirect requests.
When the Web Agent is installed on an IIS 6.0 Web Server, the Agent has the following restrictions:
- The Web Agent filter and Web Agent extension must be configured to run before other third-party filters installed on the Web server.
- The Web Agent must be configured as the first wildcard application map if it is going to protect applications running as or spawned by an ISAPI extension.
- The IIS 6.0 Web server does not enforce how third-party filters and extensions behave. IIS 6.0 processes ISAPI filters before calling ISAPI extensions, including the Web Agent extension. Therefore, the SiteMinder Web Agent for IIS 6.0 is unable to authenticate or authorize access to applications, implemented as pure ISAPI filters. This limitation impacts Web Agent integration with other third-party offerings for this IIS 6.0 Web server, if those offerings are implemented as ISAPI filters that process and/or redirect the request before ISAPI extensions are called.
