graphene-django/docs/authorization.rst

180 lines
4.8 KiB
ReStructuredText
Raw Normal View History

2016-09-21 08:30:36 +03:00
Authorization in Django
=======================
There are several ways you may want to limit access to data when
2016-09-21 08:30:36 +03:00
working with Graphene and Django: limiting which fields are accessible
via GraphQL and limiting which objects a user can access.
Let's use a simple example model.
.. code:: python
from django.db import models
class Post(models.Model):
title = models.CharField(max_length=100)
2016-09-21 08:30:36 +03:00
content = models.TextField()
published = models.BooleanField(default=False)
owner = models.ForeignKey('auth.User')
Limiting Field Access
---------------------
To limit fields in a GraphQL query simply use the ``fields`` meta attribute.
2016-09-21 08:30:36 +03:00
.. code:: python
from graphene import relay
from graphene_django.types import DjangoObjectType
from .models import Post
class PostNode(DjangoObjectType):
class Meta:
model = Post
fields = ('title', 'content')
2016-09-21 08:30:36 +03:00
interfaces = (relay.Node, )
conversely you can use ``exclude`` meta attribute.
.. code:: python
from graphene import relay
from graphene_django.types import DjangoObjectType
from .models import Post
class PostNode(DjangoObjectType):
class Meta:
model = Post
exclude = ('published', 'owner')
interfaces = (relay.Node, )
2016-09-21 08:30:36 +03:00
Queryset Filtering On Lists
---------------------------
In order to filter which objects are available in a queryset-based list,
define a resolve method for that field and return the desired queryset.
.. code:: python
from graphene import ObjectType
from graphene_django.filter import DjangoFilterConnectionField
from .models import Post
class Query(ObjectType):
all_posts = DjangoFilterConnectionField(PostNode)
2016-09-21 08:30:36 +03:00
def resolve_all_posts(self, info):
2018-09-05 14:21:39 +03:00
return Post.objects.filter(published=True)
2016-09-21 08:30:36 +03:00
User-based Queryset Filtering
-----------------------------
If you are using ``GraphQLView`` you can access Django's request
with the context argument.
.. code:: python
from graphene import ObjectType
from graphene_django.filter import DjangoFilterConnectionField
from .models import Post
class Query(ObjectType):
my_posts = DjangoFilterConnectionField(PostNode)
2016-09-21 08:30:36 +03:00
def resolve_my_posts(self, info):
2016-09-21 08:30:36 +03:00
# context will reference to the Django request
if not info.context.user.is_authenticated:
return Post.objects.none()
2016-09-21 08:30:36 +03:00
else:
return Post.objects.filter(owner=info.context.user)
2016-09-21 08:30:36 +03:00
If you're using your own view, passing the request context into the
schema is simple.
.. code:: python
result = schema.execute(query, context_value=request)
Global Filtering
----------------
If you are using ``DjangoObjectType`` you can define a custom `get_queryset`.
.. code:: python
from graphene import relay
from graphene_django.types import DjangoObjectType
from .models import Post
class PostNode(DjangoObjectType):
class Meta:
model = Post
fields = '__all__'
@classmethod
def get_queryset(cls, queryset, info):
if info.context.user.is_anonymous:
return queryset.filter(published=True)
return queryset
Filtering ID-based Node Access
2016-09-21 08:30:36 +03:00
------------------------------
In order to add authorization to id-based node access, we need to add a
method to your ``DjangoObjectType``.
.. code:: python
from graphene_django.types import DjangoObjectType
from .models import Post
class PostNode(DjangoObjectType):
class Meta:
model = Post
fields = ('title', 'content')
2016-09-21 08:30:36 +03:00
interfaces = (relay.Node, )
@classmethod
2018-09-26 21:07:50 +03:00
def get_node(cls, info, id):
2016-09-21 08:30:36 +03:00
try:
2018-09-05 14:22:54 +03:00
post = cls._meta.model.objects.get(id=id)
2016-09-21 08:30:36 +03:00
except cls._meta.model.DoesNotExist:
return None
if post.published or info.context.user == post.owner:
2016-10-19 00:30:15 +03:00
return post
return None
2018-09-05 14:22:54 +03:00
Adding Login Required
---------------------
To restrict users from accessing the GraphQL API page the standard Django LoginRequiredMixin_ can be used to create your own standard Django Class Based View, which includes the ``LoginRequiredMixin`` and subclasses the ``GraphQLView``.:
.. code:: python
# views.py
2019-04-26 18:48:37 +03:00
from django.contrib.auth.mixins import LoginRequiredMixin
from graphene_django.views import GraphQLView
class PrivateGraphQLView(LoginRequiredMixin, GraphQLView):
pass
After this, you can use the new ``PrivateGraphQLView`` in the project's URL Configuration file ``url.py``:
For Django 2.2 and above:
.. code:: python
urlpatterns = [
# some other urls
path('graphql', PrivateGraphQLView.as_view(graphiql=True, schema=schema)),
]
.. _LoginRequiredMixin: https://docs.djangoproject.com/en/dev/topics/auth/default/#the-loginrequired-mixin