graphene-sqlalchemy VS django-graphql-auth

I have a project in python 2.7 and started migrating it to 3.9, after some upgrades I started getting this error "AttributeError: entity" similar to this issue. I already googled similar issues and I think it has to do with a relationship or table class model. Is there a way I can check if my table class models and relationships created properly.

Before we add the other objects to this file, let’s discuss what we have so far. We imported our models from our models.py file. Then we are creating our class UserObject, which we can see extends the SQLAlchemyObjectType – a class provided by graphene-sqlalchemy to integrate SQLAlchemy and GraphQL. The user_id attribute tells graphene to use the id associated with the model in the database, rather than the unique id graphql provides. You don’t need to use this attribute if you don’t want to, I find it useful for my applications. Finally, we are classing the inner class Meta that allows us to set different options. We are telling graphene_sqlalchemy to use the UserModel and to use the Relay Node.

We use Django extensively in our platform to run many different aspects of our business. We use our own platform to build, pack and deploy our Django-based Single-Sign-On Identity Service that is based on this open-source: https://github.com/PedroBern/django-graphql-auth

After reading about the differences between JWT and the default DB based session mechanism which Django uses the latter seems the safest and simplest in many respects. Without graphql, logging in and signing up is easy with the default django forms and views. With graphql, I wasn't sure. In my research for handling authentication with graphql I stumbled upon django-graphql-auth (https://github.com/PedroBern/django-graphql-auth) but it seems to be based on jwt. I cannot seem to find anything else similar which supports the default django session mechanism.