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

book

Article ID: 205061

calendar_today

Updated On:

Products

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

Issue/Introduction

When running a CA Access Gateway (SPS) and after configuring the error page according to the documentation (1) with the files SPSErrorMessages.properties and WebServerErrorMessages.properties 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.

Environment

CA Access Gateway (SPS) 12.8SP3 on Linux

 

Resolution

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

      <error-page>
       <error-code>404</error-code>
       <location>/Error404.jsp</location>
      </error-page>

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