Make session security context available for both WebSocket protocols #1313
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.
Pull request checklist
first
Pull Request type
Changes in this PR
Initial Issue see: #814 - This fixes a bug where we do not receive the SecurityContext when using
WebsocketGraphQlTransportWSProtocoll
. The logic which is used inWebsocketGraphQLWSProtocolHandler
where the SecurityContext is loaded from the session, should be called regardless of which protocol is used. So i moved the logic up again toDgsWebSocketHandler
where it was before so it gets calledAlternatives considered