Introduction

We have already discussed the main reason for using Cerbos, which is to get rid of writing a whole lot of conditional code for managing the roles and their corresponding permissions, but it is not the only thing about using an externalized policy-based authorization system.

Let’s discuss some other advantages that developers can take by using Cerbos.

1. As we have separated the policies for all the roles that are there in our system, it will be very easy and efficient to manage and make changes in the permissions of the roles, if necessary.




2. Irrespective of any authorization technique, such as JWT tokens, or Auth0, Cerbos authorization service can read data from any of the authentication techniques.




3. Cerbos authorization services can be deployed on any system, such as Cloud Providers, Serverless Architectures, Deployment using Kubernetes environment etc.




4. Cerbos’s authorization services can be integrated via SDKs with any of the programming stack/languages, such as .NET, JavaScript, Python, Java, Ruby, Rust and many others.

Cerbos PDP

Cerbos Hub

.

Cerbos Playground

.

All these will make you more familiar with the Cerbos system so that you can be able to write your own policies and give specific access to specific roles.

You can also learn about how to write policies in Cerbos from

So, folks, we have come to the end of this article.


We have discussed an awesome externalized system of authorization named Cerbos

Here are all the necessary links that you need to get started using this awesome product.

Cerbos PDP → 🔗


Cerbos Playground → 🔗 https://play.cerbos.dev/new

If you have any queries or comments about this article then please reach me out on [email protected].