STCOR-930 correctly dispatch rtrFlsWarningTimeout #1579
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
setRtrFlsWarningTimeout()
now sendsrtrFlsWarningTimeout
rather thanrtrFlsTimeout
. This bug was introduced in PR #1511 (ontokeycloak-quesnelia
), which looks like a bad copy-pasta from PR #1510 (ontokeycloak-ramsons
).When RTR is correctly configured such that sessions end at a fixed (static) datestamp, this change will have no effect: the original timer will not be canceled when the tokens rotate, but it won't matter because the end-point isn't moving, meaning the original timer will remain accurate.
When RTR is incorrectly configured, however, and a session's end-point is extended on rotation as in a sliding window, this change resolves a bug that would cause the session-timeout banner to display a "Time remaining: 00:00" message without actually ending the session. This occurred because the original timer would not be canceled when the tokens rotated even though a new, later end-point had been established.
Refs STCOR-930