Conversation
|
I implemented cookie/session lifetimes in infrastructure-idm ... I believe that the lifetime is an application concern, rather than a parameter to the .read() method. To this end, I'd suggest something in config.yaml and/or a parameter when the app is constructed, which is then used to restrict all session lifetimes regardless of .read() usage. And to be clear: the quart session cookie has an HMAC on it, to prevent tampering. That is the purpose of |
Updated documentation to reflect changes in session handling options.
|
I've put it in there as a config parameter instead of an argument. In ATR we load our config programmatically ( |
We implemented a maximum session lifetime as part of the Trusted Releases platform, but thought we should contribute it back. Feedback welcome!