Originally posted by kristjanvalur February 13, 2022
...
Alternatively, is there a way to intercept and handler the connection_init
message and either accept or reject the conneciton based on the request headers (from the original connection) or the optional payload
and attach custom data to the resulting connection
object?
Basically, I'm searching for the canonical way to do request authentication and authorization when working with requests that arrive via the graphql-transport-ws
transport, be they subscriptions, mutations or queries.
Cheers!
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too