[ELY-1503] Ensure the reference to the GssContext and KerberosTicket can be dropped during Serialization. #1097
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ializing on a distributed session.
|
So the point is, SESSION scope will prevent sharing GSSContext between multiple sessions in one connection, but it will be dropped on replication between servers, so new negotiation will be initiated when switching to different server? |
|
Yes so on fail over a new authentication will need to occur, we may also want to switch on Clustered SSO at some point but as SPNEGO silently fails over anyway we didn't switch that on as Clustered SSO would not propagate any delegated credential. |
hkalina
approved these changes
Feb 20, 2018
fjuma
approved these changes
Feb 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Also [ELY-1518] Elimination of a stream and lambdas where a for loop can be used.
https://issues.jboss.org/browse/ELY-1503
https://issues.jboss.org/browse/ELY-1518