ksPath entry in .jrsksp file no longer exists in JasperReports® Server 7.8+

Issue:

In JasperReports® Server 7.5, there was a requirement to update the keystore files as documented in the article "Encryption in JasperReports Server 7.5+" (see Related Article section). The specific section of the article is "Updating Keystore files" which details steps to base64 decode the .jrsksp file, modify the ksPath property and base64 encode the file back.

However, in JasperReports® Server 7.8, the ksPath no longer exists as a property.   What is the reason for this and is it still required to update the keystore properties file ?

Solution:

The ksPath was there in the .jrsksp file when the enhanced security encryption of keys started in JasperReports® Server 7.5. But from JasperReports® Server 7.8+, Jaspersoft Engineering decided to make configuration of keystore files location easier by eliminating it from the .jrsksp property file.

The updating of the keystore files location by manually doing a base64 decoding and encoding of the .jrsksp is no longer necessary. 

The user can update the WEB-INF/classes/keystore.init.properties and set "ks" and "ksp" to a different path and then relocate the keystore files to this path having the appropriate directory permissions for the user account. 

The order of inspection of the keystore files location remain the same as documented in the above referred article :

- “ks” and “ksp” environment variables

- WEB-INF/classes/keystore.init.properties: ks, ksp properties

Typically the keystore files are stored in the user's home directory.

Note that modifying the keystore.init.properties requires a restart the JasperReports application server.

Related Articles:

https://community.jaspersoft.com/wiki/encryption-jasperreports-server-75