Cc Countersign Authorization with airSlate SignNow

Cc countersign authorization

hi everyone my name is Milan and welcome to part three of the permission authorization Series in this video we're finally going to see how we can Implement our custom authorization Handler so that we can get authorization properly working in our API using permissions let's see how we're going to implement this in part one of this series we defined our has permission attribute and our permission enum and I said that we were going to implement authorization on our endpoints using this approach in part 2 I showed you how we can configure the roles and permission entities and see the initial values for the roles and permissions using energy framework migrations and finally in part 3 we are going to implement our custom authorization Handler so let's start with that right away inside of the infrastructure project I'm going to add a new class which is going to be our custom authorization Handler I'm going to name it permission authorization Handler we're going to use this class to implement the authorization Handler class and add the authorization Logic for handling permissions so we need to inherit from the authorization Handler class if you take a look at this class you can see that it has a generic argument which represents the authorization requirement for this authorization Handler an authorization requirement is just a class that's implementing the eye authorization requirement interface so we are first going to need to add a requirement before we can implement the authorization Handler so let's go ahead and do that I'm going to add a new class which is going to be our permission requirement what we need inside of the permission requirement is to implement the eye authorization requirement interface so I'm going to go ahead and do that this interface is simply a marker interface and doesn't contain any properties but we are going to need to define a property on our permission requirement that is going to tell us what is the permission that we are handling for this authorization request so let's add a simple property that is going to contain our permission it's going to be a string property and I'm going to add our Constructor so that we can initialize a new instance of our permission requirement now that I have our permission requirement I can go back to the permission authorization Handler and specify this requirement as the generic argument on the authorization Handler class and now we can go ahead and implement the missing members we need to overwrite and implement the handle requirement async method on the authorization requirement and this is where we are going to take the permission on the permission requirement and see if the currently authenticated user has this permission and if so then we can allow him to continue the execution and access the endpoint that he is trying to access the first thing that we are going to do is we are going to get the...