Ludovic Farine created BROOKLYN-621:
---------------------------------------
Summary: Session should have absolute expiry period in addition to
inactivity expiry period
Key: BROOKLYN-621
URL: https://issues.apache.org/jira/browse/BROOKLYN-621
Project: Brooklyn
Issue Type: Improvement
Affects Versions: 1.0.0-M1
Reporter: Ludovic Farine
Fix For: 1.0.0
The `MultiSessionAttributeAdapteradapter` expires after inactivity but some
customers have a requirement to force a re-login after a (usually longer eg
12h) period of time even if there is activity.
This should be a setting e.g. in `brooklyn.cfg`:
`brooklyn.ui.session.expiry.absolute` -- read in as a `Duration` and if null,
0, negative, then ignored
One implementation would be brooklyn sets e.g. a `last-login-time` attriibute
on successful login, and on access _if_ the key above is set in
mgmt().brooklynConfig(), then it checks and forces expiry/reset of the session
if expired.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
