Initiate logout for all logged on states #172
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.
fixes #170
related to #171
The logout sequence has stopped working due to the logout initiation being coupled to the
inSessionstate. As identified in #171, we were seeing the session immediately sending a test request after logon. By doing so, the session state transitioned frominSessiontopendingTimeout. While thependingTimeoutstate embeds theinSessionstate, the call toapplication.Stoponly checks if the current state is theinSessionstate to initiate the logout sequence.These changes move
initiateLogoutinto the session, so the action onStopcan checkIsLoggedOn, and initiate the logout sequence as necessary. Therefore all states that confirm true for theIsLoggedOnfunction interface, will result in a proper logout sequence.