graphql-auth | One approach to authentication/authorization | GraphQL library

The following is a more thorough reproduction of solution found here.

We basically need to override the jwt_payload method that comes as part of the graphql_jwt package.

Add this to project's settings.py

In order to tackle the above issue I have adapted the graphql-auth-directives package and created my own, see here. This allows you to create such 'conditional permissions' as I have called them. To get a better understanding of the implementation I'd suggest you to look at the Medium article I wrote about it.

The object returned inside your resolver includes a property named user, but your field is named users. Since users is undefined, it resolves to null, but the field is non-nullable, so an error is thrown instead.

N.B. It's going to be a little difficult to answer this without seeing how your settings.py is configured, but double-check that you went through every step. I went through the quickstart too but still missed a few spots.

I ran into a similar "Connection refused" error, but the issue was that my settings were not configured properly.

Edit: After further local development and toggling with individual settings, I realized that my "Connection refused error was related to not having EMAIL_BACKEND configured. It was trying to connect to any SMTP server that wasn't running. Make sure you have EMAIL_BACKEND = "django.core.mail.backends.console.EmailBackend" set to log this functionality to your console.

Here's a slightly abbreviated copy of my settings.py from a scratch project I was using, just to be sure that you have it configured correctly:

Source: django-graphql-auth quickstart.

N.B.: It's a little long, make sure to scroll all the way through

You will have to use the 'useMutation' hook provided by apollo

the code would be be like below

I'm the author of the package. Now the documentation site has a custom user model in the quickstart, you can see it here. Currently, it's not documented how to use it with a custom user model, but it is already an open issue, you can see it here. I will paste the same answer that is on the Github.

From Django docs:

Changing to a custom user model mid-project

Changing AUTH_USER_MODEL after you’ve created database tables is significantly more difficult since it affects foreign keys and many-to-many relationships, for example.

So, make sure to create the custom user model when you start your project.

Following the Django custom user model.

You aren't installing the requirements in your dockerfile, so the dockerized environment doesn't have Flask.

Add

The post I had linked was already giving enough information to solve the problem.

I was stubbornly hooked on the usage of mutation because I didn't have enough knowledge on GraphQL to know what makes it different from query.

Abandoning mutation and using query is enough to solve the problem.

So I have a