Custom Error Pages don't work in CA Access Gateway (SPS) Secure Proxy
search cancel

Custom Error Pages don't work in CA Access Gateway (SPS) Secure Proxy


Article ID: 205061


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER


When running a CA Access Gateway (SPS) and after configuring the error page according to the documentation (1) with the files and then the CA Access Gateway (SPS) keeps showing the default messages, and not the customized ones:

HTTP Status 400 - Bad Request Message Invalid request. There request contains incorrect syntax or no parameters valid. Transaction ID: 191xxxxx-xxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx-407 failed.

This happens when the users reach the Service Provider federation.


CA Access Gateway (SPS) 12.8SP3 on Linux



According to documentation (2), modify the content of the configuration for the Federation Services in the Web.xml file.

Add the custom code to catch the HTTP return code as per the <error-page> tab (3) such as


Again, according to the same documentation, the Web.xml is the file to put all the customization. This configuration will be supported as long as these customizations aren't involved in issues.  

Additional Information

(1) Modify the Default Custom Error Pages

(2) The Web.xml File

(3) How to Handle Error in Web.xml for Java web applications