thanks @mattly ill check it out 😄

Hello, has anyone managed to authenticate over websockets in order to have authenticated subscriptions? I am using lacinia-pedestal, as far as I see something like this is not supported (yet)? https://www.apollographql.com/docs/graphql-subscriptions/authentication.html

@jerben we are using cookies to authenticate, we use the init-context argument to get the cookie off the upgrade request and decide whether to allow the upgrade to go ahead

there's an open issue for this on lacinia-pedestal if i remember correctly

@oliy Cool thanks for the hint, I will try it out! 🙂

@jerben I did it sometime, but in this case you first had to login on a page, then the username would be stored in the session, and only with a user with certain roles the websocket was initiated

I’m trying to add auth to lacinia-pedestal setup, I basically just put and auth interceptor in the service map (-> (lacinia/service-map ...) ... (assoc ::pedestal/interceptors [(auth/check-auth auth)]) (pedestal/create-server)).

Is this the right way of doing things? I’m getting non descriptive {:msg "sending error", :message "Internal server error: no response", :line 214} error when the auth succeeds

Or maybe let me rephrase: How do I add an interceptor in front of all lacinia-pedestal routes and not break anything?

@nooga Regarding queries/mutations, we currently read an auth token from the context in the resolver function and resolve accordingly.

I managed to inject the auth interceptor this way

I just discovered that field names in lacinia have to be simple keywords, no namespaces allowed. Anyone know whether that's ultimately a limitation of GQL, or if it's just lacinia?

It is in accordance with the GraphQL spec.

Damn, ok. That doesn't play so nicely with clj's love of namespaced keywords 😜

Thanks!

I wish the GraphQL folks had talked to us Clojure folks before going off and designing something.😉

I know, right? 😉