Jaspersoft Organization ID in caps creates keys in mixed case

Products

• Clarity PPM On Premise

Issue/Introduction

As part of the Clarity Report service integration setting in CSA or properties.xml, when you enter the Organization ID in upper case like 'EXAMPLE' and you run the clarity admin command to create keys (admin jaspersoft keystore) the following keys are created:

• EXAMPLE.jks
• example.properties

Observe one of the keys is in lowercase

The problem caught on a specific Clarity on-premise environment implementation where automation was used to copy the Keys(.jks and .properties) to all the Jaspersoft cluster nodes, i.e. <Tomcat>/webapps/reportservice/WEB-INF/config

The automation could only find the key with the small letters but not the one with the capital letters. It couldn't copy it to the Tomcat directory, and the Clarity Advanced reporting navigation breaks. 

Indications:

Advanced reporting navigation fails with authorization errors Error 401 - User Not Registered | Error User is not registered on the reporting server.

The clarity admin command (admin update jasperParameters) to run sanity checks also fails

 

Login success, but Unauthorized access to http://report_service_url:port/reportservice with username ppmjasperadmin

Create and update jaspersoft user job fails:

Failed to get an instance of ClarityJasperAdmin :: Exception getting ClarityJasperAdmin : Unauthorized access to http://report_service_url:port/reportservice with username ppmjasperadmin

Environment

16.2.x with Jaspersoft Report Server 9.0

Resolution

Manually copy the jks key (EXAMPLE.jks) to the Destination Jaspersoft directory :<Tomcat>/webapps/reportservice/WEB-INF/config

Or

Ensure the automation ignores uppercase and lowercase. For example with "-iname"

• find -iname example.properties will find both example.properties and EXAMPLE.properties