Cap max session time to a safe value. #144
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.
This change fixes issues with immediate expiration of agent sessions created with
com.iplanet.am.session.agentSessionIdleTime
system property set to a non-zero value.The original issue was that when the
agentSessionIdleTime
was set, then max session time was set toLong.MAX_VALUE
, which caused value overflow ingetMaxSessionExpirationTime
and the session was immediately marked as expired.The issue led to a quite strange behavior of not including
tokenId
field in REST/authentication
response: