The security cache system temporarily stores security objects such as users, roles, groups and ACLs. ACL, short for Access Control List, is the core object of the security authorization system, and is in charge of storing and checking principal permissions. When JReport Enterprise Server requires information from the security system, it can fetch it from the cache for better performance.
The cache system caches not only security objects for the built-in security system, but also those implemented by the security API from the external security system. It caches security information in the security data. If the security service needs security information, it will fetch it from the security data. However, if the security data cannot find the information, it will request it from the security API, and then cache it in the cache system. When the security information is modified in the security system, the security API is invoked directly in order to modify the security data.
Note: There is a special interface SecurityListener in the cache system, through which the cache is noted to update the cached information. It is recommended that you invoke it when you access the external security system, so as to synchronize security data between the cache system and the external security system.
The following focuses on the configuration and synchronization of the security cache system: