After upgrade to 12.1.01.04 WCC UI lets the users authenticated but then just spinning hour glass and does not show anything
search cancel

After upgrade to 12.1.01.04 WCC UI lets the users authenticated but then just spinning hour glass and does not show anything

book

Article ID: 419498

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

After upgrade from 12.0.1 to 12.1.01 and cumulative#4 there after (12.1.01.04), WebUI lets users authenticated successfully, but nothing else happens after.  Web page just spins like below

If you enable browser console, it seems to show that the call to  ipce.min.js  is erroring out for some reason

Cause

$CA_WCC_INSTALL_LOCATION/tomcat/conf/server.xml did not contain the needed IPCE security content valve definition in it.  It normally looks like this:

<Valve className="com.ca.wcc.catalina.ContentSecurityPolicyValve" enable="true" value="default-src 'self';connect-src 'self' https://*.ipce.broadcom.com https://www.youtube.com; img-src 'self' data:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.ipce.broadcom.com https://www.youtube.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://*.ipce.broadcom.com https://www.youtube.com; font-src 'self' https://fonts.gstatic.com; frame-src 'self' blob: https://www.youtube.com; frame-ancestors 'self';"/>

 

This is because, after the upgrade in this case, an old server.xml (from a previous release) was copied over instead of making any needed changes to the correct server.xml
                        
       

Resolution

  • Ensure the server.xml is a valid 12.1.01.04 release one
  • Check if the XML tag for the ContentSecurityPolicyValve matches the one indicated in the cause section above
  • If not, copy a valid 12.1.01.04 server.xml from another server (or reinstall)
  • Make any needed changes (for example, to the HTTPS connector) to the good server.xml and restart CA-wcc-services
  • Empty browser cache and retry the URL (without emptying this cache, the old page/policies would still apply and the behavior of spinning webpage will not change)