Configuring custom error page in CA Release Automation


Article ID: 129944


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


Improper Error handling messages reveal implementation details that should never be revealed. Such details can provide hackers important clues on potential flaws in the site and such messages are also disturbing to normal users.

Some of the details are like Tomcat Version, CSRF tokens etc. The Error page is also not user friendly.

In scenarios of most common error like 401, 403, 404 Release Automation displays the default page of application (as per product design). In some end-user scenario there is a need to have more user-friendly pages abstracting information which are rendered on browser in default behavior. For example the 403 Access Denied error page message will be something like below.

HTTP Status 403 - Invalid CSRF Token 'CSRF_TOKEN_ID' was found on the request parameter '_csrf' or header ...

The default error pages doesn't suffice to all end-users need and in some cases end-user wish to show custom error message, tend to be non-technical and user friendly.


CA Release Automation : 6.5,6.6 or higher


Please follow steps on configuring custom error pages for Release Automation

1: On Nolio Automation Server (NAC a.k.a DMS i.e. Data Management Server) navigate to directory  ReleaseAutomationServer\webapps\datamanagement\WEB-INF\
2: Locate the file web.xml and add below lines for respective error-code above </web-app>. In case if you want to only add very specific error code please only add those and skip others.

3: Create the custom error pages at path  ReleaseAutomationServer\webapps\datamanagement\ mapped in above configuration for respective error-code. For example in above configuration error-code 404,403 & 500 are mapped to error.html
4: Restart the NAC service


1558688487390000129944_sktwi1f5rjvs16fmc.png get_app