Mod_Auth_Cas fix allows DotNetNuke to work

We’re using mod_auth_cas on a linux reverse proxy to authenticate users to our DotNetNuke (DNN) intranet site.? After dealing with the entropy problem that was really slowing down access, we had just one problem remaining:? files that were attached to DNN pages with the built-in editor were not accessible through the reverse proxy.

It turns out that DNN uses a “fileticket” parameter in the file link URLs, and mod_auth_cas uses a “ticket” parameter.? But mod_auth_cas was mistakenly stripping out DNN’s fileticket parameters.? A DNN URL would look like this: “/LinkClick.aspx?fileticket=DBDQlsksjlefwgb&tabid=70”.? After going through the reverse proxy, mod_auth_cas had mangled it to “/LinkClick.aspx?filetabid=70”.

Someone involved with mod_auth_cas pointed me to the bug tracker, and there was a fix for the URL mangling.? You need to get the latest source files, compile them, and the issue is gone!

Leave a Reply

Your email address will not be published. Required fields are marked *