Blog Viewer

Tech Tip - CA Single Sign-On: Web Agent : SiteMinder and ASP.NET MVC

By Ujwol posted 04-14-2016 02:11 AM

  

Problem Summary

With SiteMinder configured, ASP.NET MVC Website shows HTTP 404 when application pipeline mode is integrated.

However, if SiteMinder is unconfigured, ASP.NET 4.5 MVC Website works without any issue when application pipeline mode is Integrated.

 

Environment

  • Web Agent Version : R12.52 SP1, R12.5
  • Web Server : IIS 7.5
  • ASP.NET version: - ASP.net

 

Root Cause

When SiteMInder is enabled, somehow for the integrated pipeline mode the "UrlRoutingModule-4.0 " is not triggered.
This module is required for the MVC routing to work for the extension less Url.

 

Solution

  1. Set runallmanagedmodulesforallrequests=true
    This is not a recommended approach , as this means that all the managed module will be run for all the request irrespective of the "managedHandler" precondition.
  2. An alternate and better configuration would be enable the SiteMInder handler for the Integrated Pipeline mode also :
    i) Change :

<add name="handler-wa-32" path="*" verb="*" modules="IsapiModule" scriptProcessor="C:\F6\CA\webagent\win32\bin\ISAPI6WebAgent.dll" resourceType="Unspecified" requireAccess="None" preCondition="classicMode,bitness32" />


To :
<add name="handler-wa-32" path="*" verb="*" modules="IsapiModule" scriptProcessor="C:\F6\CA\webagent\win32\bin\ISAPI6WebAgent.dll" resourceType="Unspecified" requireAccess="None" preCondition="bitness32" />


ii) Change :
<add name="handler-wa" path="*" verb="*" modules="IsapiModule" scriptProcessor="C:\F6\CA\webagent\win64\bin\ISAPI6WebAgent.dll" resourceType="Unspecified" requireAccess="None" preCondition="classicMode,bitness64" />

 

To:
<add name="handler-wa" path="*" verb="*" modules="IsapiModule" scriptProcessor="C:\F6\CA\webagent\win64\bin\ISAPI6WebAgent.dll" resourceType="Unspecified" requireAccess="None" preCondition="bitness64" />

Basically, remove the "classicMode" precondition from the SiteMinder Handlers.
With this change in place, the UrlRoutingModule-4.0 triggered properly and the MVC website worked as expected.

References

https://msdn.microsoft.com/en-us/library/dd381612(v=vs.98).aspx

0 comments
2 views