Password changes are not immediately reflected in a clustered JasperServer environment

Scenario:

You have two JasperServers in a cluster and you change the password for the user on one server. After changing the password for the user, the user sometimes cannot log in for some time with the new password and has to wait. Why does that happen and how can this be prevented?

Solution:

JasperServer uses ehcache to build repository, permissions and other caches. When you have two nodes running in a cluster you need to configure the cache to be distributed and synchronized, otherwise two nodes will build their own caches and they will eventually get desynced with the actual state of repository database.

There are three ways to sync the caches:
RMI - requires you to enable IP multicasting
JMS - requires a queue server, like ActiveMQ or RabbitMQ
Amazon SNS - requires purchasing service from Amazon

You can pick any of the three methods and configure the cache config files accordingly. Please take a look at this chapter of documentation for more details about this:
https://community.jaspersoft.com/documentation/tibco-jasperreports-server-ultimate-guide/v790/sample-configurations

This needs to be done on both nodes. You will need to configure the files ehcache.xml and ehcache_hibernate.xml.