info hook avoiding extend session #1279
Unanswered
fnieri-cdp
asked this question in
Q&A
Replies: 2 comments 3 replies
-
this is a pretty much undocumented feature with a clumsy implementation so far: the functionality works because the session is not written to the cache... ; however, the inactivity timeout value in the current session that is loaded in memory is updated and represented as such in the response from the info hook; but since it is never saved to cache, the actual timeout will occur as expected on subsequent requests (that load the session from cache with the original value) |
Beta Was this translation helpful? Give feedback.
2 replies
-
see fed0f2f |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I read that from release 2.4.14.2 there was the support for
extend_session=false
query parameter to the info hook to avoid extending the session on calls to the info hook.I'm using release 2.4.14.4 and I assumed calling
auth/redirect_uri?info=json&extend_session=false
, thetimeout
value in the json response wasn't going to change. Instead repetitively calling the previous endpoint, every minutes the value of attributetimeout
changes showing a session renewal.Can anyone tell me if I'm doing something wrong, I assumed incorrect behavior or if the feature is no longer present?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions