Viljami Linna
Viljami Linna
## Problem description: `django_graphql_jwt` provides nice decorators to protect queries and mutations. However there is no easy way to protect GraphQL view to non-authenticated users. When using basic django authentication...
# Prerequisites * [ ] Is it a bug? * [x] Is it a new feature? * [ ] Is it a a question? * [ ] Can you reproduce...
# Prerequisites * [x] Is it a bug? * [ ] Is it a new feature? * [ ] Is it a a question? * [ ] Can you reproduce...
**I'm submitting a ...** (check one with "x") ``` [x] bug report => see 'Providing a Reproducible Scenario' [] feature request => do not use Github for feature requests, see...
# Prerequisites *Feel free to just say what you want and remove this template.* * [x] Is it a bug? * [ ] Is it a new feature? * [...
# Description Allow modify UserType fields to return or filter extra information of the custom user ## Expected behavior All CustomUser model fields should be returned along UserType in mutations...
## Expected behaviour Every time, a new refresh token is obtained, an old refresh token should be revoked. A proper way to use refresh tokens & JWT tokens - JWT...
# Description There are multiple problems - By default Django secret key is used to decode and encode JWT keys, When using asymmetric keys, we should be able to use...
**Note: for support questions, please use stackoverflow**. This repository's issues are reserved for feature requests and bug reports. * **What is the current behavior?** We have types: ``` ChildType(graphene.ObjectType): enabled...