Ok true 👍 And I was wrong, ContextWebFilter is for incoming and ExchangeFilterFunction for the outgoing requests via WebClient. However, the Reactor/Security Context (also GRAPHQL_CONTEXT_KEY) is not present there.
The requests outside of graphq-kotlin handling have a populated Context.
The Problem is also there outside of the FilterFunction.
val reactorContext =
in a resolver function won't return the context
07/10/2020, 2:36 PM
problem is due to the reliance on graphql-java….
basically it needs completable future which means that underlying call chain is broken
and you won’t get anything in reactor context
07/10/2020, 2:37 PM
True, I noticed when inspeciting the parent contexts