Flush Configuration errors with Expired Request

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

In a Clarity environment that has 'tokenCacheStrategy="session"' configured in properties.xml file, when user navigate to the 'System Caches' page and click on 'Flush Configuration' 
then an 'Expired Request' page with 'An expired request has been detected. Request has been cancelled' alert.

 

Steps To Reproduce:

1. Log into a Clarity environment where the properties.xml has 'tokenCacheStrategy="session"' configured as a parameter
2. Go to Clarity classic home page and navigate to 'System Caches' page - https://servername/niku/nu#action:security.caches
3. Click on 'Flush Configuration' button

 

Expected: Caches get cleared

Actual: An 'Expired Request' page with 'An expired request has been detected. Request has been cancelled' alert is displayed

Environment

Clarity 16.3.1, 16.3.2

Cause

DE172170

Resolution

Resolved in Clarity 16.3.3

Additional Information

An example of a properties.xml file where tokenCacheStrategy="session" is configured

 

<applicationServer vendor="tomcat" useLdap="false" home="c:\ca\tomcats\apache-tomcat-7.0.26" adminPassword="xxxxxx" externalUrl="" tokenCacheStrategy="session">

   <applicationServerInstance id="app" …/>

    <applicationServerInstance id="nsa" …/>

  </applicationServer>