Vojtěch Dohnal

> I also tried to launch tekkit and Hexxit II without success, for the first one I get the following error: > >  > > for the hexxit II:...

> > > I also tried to launch tekkit and Hexxit II without success, for the first one I get the following error: > > >  > > >...

Hello, Thanks for submitting the issue. It looks to me as if you were using the ASGI app with the synchronous jwt middleware. Could you please verify that this is...

> @KundaPanda We are using `AsyncStatusHandlingGraphQLView` with `AsyncJSONWebTokenMiddleware` Okay so that seems in order. Are you running the app with an ASGI-capable server as well (daphne, uvicorn, hypercorn)? This seems...

That explains it then. You need a proper ASGI server to send ASGI requests -- runserver and runserver_plus both serve WSGI only. Internally this seems to work for you because...

Just encountered this quite randomly as well. We had to create our own subclass to solve this. Good thing the redis helm chart has flushdb disabled by default.

Hi, I am afraid that using a third-party identity server, such as Keycloak, and utilizing its' OIDC or other tokens is not currently possible. This library manages all the access...

Yes I have tracked down some code that might cause this, looking into it now.

Hi, thanks for creating this issue. I myself do not agree with many design choices taken by the original authors of django-graphql-jwt, but doing a complete rewrite would be very...