- Django Keycloak Auth
Django Keycloak Auth is a simple library that authorizes your application's resources using Django Rest Framework.
This package is used to perform authorization by keycloak roles from JWT token. Both realm roles and client roles are supported.
For example, the following token indicates that the user has the realm role "manager" and the client roles "director" and "employer" :
...
"realm_access": {
"roles": [
"manager"
]
},
"resource_access": {
"first-api": {
"roles": [
"director",
"employer",
]
}
},
...
For review see https://github.com/marcelo225/django-keycloak-auth
Package link: https://pypi.org/project/django-keycloak-auth/
If you have recognized my effort in this initiative, please buy me a coffee when possible.
$ pip install django-keycloak-auth
$ python setup.py install
Please report bugs and feature requests at https://github.com/marcelo225/django-keycloak-auth/issues
The MIT License (MIT)
Copyright (c) 2020 Marcelo Vinícius
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Lead Developer - Marcelo Vinicius
Co-authored-by:
- In your application
settings.pyfile, add following Middleware:
MIDDLEWARE = [
#...
'django_keycloak_auth.middleware.KeycloakMiddleware',
#...
]
#...
# Exempt URIS
# For example: ['core/banks', 'swagger']
KEYCLOAK_EXEMPT_URIS = []
# LOCAL_DECODE: is optional and False by default. If True
# tokens will be decoded locally. Instead of on the keycloak
# server using the introspection endpoint.
# KEYCLOAK_CACHE_TTL: number of seconds to cache keyclaok public
# keys
KEYCLOAK_CONFIG = {
'KEYCLOAK_SERVER_URL': 'http://localhost:8080',
'KEYCLOAK_REALM': 'TEST',
'KEYCLOAK_CLIENT_ID': 'client-backend',
'KEYCLOAK_CLIENT_SECRET_KEY': 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
'KEYCLOAK_CACHE_TTL': 60,
'LOCAL_DECODE': False
}from rest_framework import viewsets, views
from . import models, serializers
from rest_framework import status
from django.http.response import JsonResponse
from rest_framework.exceptions import PermissionDenied
class BankViewSet(viewsets.ModelViewSet):
"""
Bank endpoint
This endpoint has all configured keycloak roles
"""
serializer_class = serializers.BankSerializer
queryset = models.Bank.objects.all()
keycloak_roles = {
'GET': ['director', 'judge', 'employee'],
'POST': ['director', 'judge', ],
'UPDATE': ['director', 'judge', ],
'DELETE': ['director', 'judge', ],
'PATCH': ['director', 'judge', 'employee'],
}
def list(self, request):
"""
Overwrite method
You can specify your rules inside each method
using the variable 'request.roles' that means a
list of roles that came from authenticated token.
See the following example bellow:
"""
# list of token roles
print(request.roles)
# Optional: get userinfo (SUB attribute from JWT)
print(request.userinfo)
return super().list(self, request)class CarViewSet(viewsets.ViewSet):
"""
Car endpoint
This endpoint has not configured keycloak roles.
That means all methods will be allowed to access.
"""
def list(self, request):
return JsonResponse({"detail": "success"}, status=status.HTTP_200_OK)class JudgementView(views.APIView):
"""
Judgement endpoint
This endpoint has configured keycloak roles only GET method.
Other HTTP methods will be allowed.
"""
keycloak_roles = {
'GET': ['judge'],
}
def get(self, request, format=None):
"""
Overwrite method
You can specify your rules inside each method
using the variable 'request.roles' that means a
list of roles that came from authenticated token.
See the following example bellow:
"""
# list of token roles
print(request.roles)
# Optional: get userinfo (SUB attribute from JWT)
print(request.userinfo)
return super().get(self, request)When you don't put keycloak_roles attribute in the Views that means all methods authorizations will be allowed.
When if you use api_view decorator, you would write a very simple @keycloak_roles decorator like this:
from django_keycloak_auth.decorators import keycloak_roles
...
@keycloak_roles(['director', 'judge', 'employee'])
@api_view(['GET'])
def loans(request):
"""
List loan endpoint
This endpoint has configured keycloak roles only
especific GET method will be accepted in api_view.
"""
return JsonResponse({"message": request.roles})Before everything, you must install VirtualEnv.
# Install venv in root project folder
$ python3 -m venv env && source env/bin/activate
# Install dependencies
$ pip install -r requirements.txt
# Run tests
$ python manage.py test
Warning: before you update this package, certifies if you'll change the version in
setup.pyfile.
If you interested contribute to developing this project, it was prepared a tiny tutorial to install the environment before you begin:
# Install venv in root project folder
$ python3 -m venv env && source env/bin/activate
# Update packages for development
$ python -m pip install --upgrade -r requirements.txt
# Generate distribution -> it's on me for while ;)
$ python setup.py sdist
# Checks if the package has no errors
$ twine check dist/*
# Upload package -> it's on me for while ;)
$ twine upload --repository-url https://upload.pypi.org/legacy/ dist/*
- Run following command on terminal to up Keycloak docker container:
# in root project folder
$ docker-compose up-
Open http://localhost:8080/ in your web browser
-
Create the following steps:
realm,client(as confidential) and yourclient secretaccording the settings.py file- Client Roles:
director,judge,employee - Create a new user account
- Vinculate Client Roles into above user account
-
Run following command on another terminal:
# Install venv in root project folder
$ python3 -m venv env && source env/bin/activate
# Install dependencies for this library
$ python -m pip install --upgrade -r requirements.txt
# Generate a local distribution for django-keyclaok-auth
# Change the version of this library if necessary
$ python setup.py sdist
# Generate a local dist (verify version)
$ pip install dist/*
# Create migrations, fixtures and run django server
$ python manage.py makemigrations && \
python manage.py migrate && \
python manage.py loaddata banks.json && \
python manage.py runserver- Starting development server at http://127.0.0.1:8000/
- Use Insonmina or Postman to test API's endpoints using Oauth2 as authentication mode.