Details
-
Bug
-
Status: Closed
-
Top
-
Resolution: Fixed
-
None
-
None
Description
When a change below /hippo:configuration happens, odds are this is in the area of the security domains. Only newly created sessions will 'see' changes in security (for example a changed hippo:domain). Existing jcr sessions won't get these changes pushed.
Since a jcr session in a hst pool can live forever (certainly in low traffic sites), this means, a change in security domains might never make it to a hst pooled session as long as the application is not restarted.
I think we can better clear all sessions in all pools after any change below /hippo:configuration
Attachments
Issue Links
- relates to
-
HSTTWO-2576 Backport : HST session pools should be cleared after any change below /hippo:configuration
- Closed
-
HSTTWO-2577 Backport HST session pools should be cleared after any change below /hippo:configuration
- Closed
-
HSTTWO-3324 PoolingRepositorySessionMustBeLoggedOutListener does not need to check HippoNodeType.HIPPO_PASSKEY event any more explicitly
- Closed