API request signing in Django (2)

Adding a permission layer

This article is the second and final part on API request using Django Rest Framework. In the first part we explained what API signing is, why and how to apply it in your Django projects. Basically, we implemented the API signing functionality as a middleware in Django. You can check and review the first part here.

Sometimes you want to have more control on your endpoints, so you may decide that for some endpoints you want to bypass the API signature. Also, maybe you want this signature-check to be done not in a middleware layer, but in the permission layer instead.

Django Rest Framework Permission Class

So, you can have more control on when API signing should be applied in different ways; you can implement it as a decorator class or function or you may implement it as class that is only invoked whenever you explicitly want. One of the ways also is to implement it in the permission layer provided by the framework you use. Since Django Rest Framework one of the mostly used frameworks to build API in Django, I’ll present how we can implement the API signing in DRF permission layer.

Create a file called app/signing_permission.py which contains a custom DRF permission class. Actually it is the same as the middleware, but instead of implementing the __call__ method, we are implementing a has_permission method in a class inherited from BasePermission:

API Signing for Django and DRF Package

I’ve built a package that letting you doing the API Signing in DRF projects with a matter of some configurations in the settings (drf-simple-api-signing). I highly encourage you to check it, contribute, use and report issues and bugs. Yet, there is a lot that can be enhanced and added to this package, but it will provide you with all you want to start with.

Have some doubts or thoughts to share? Feel free to leave a comment or reach out to me directly on Twitter.