Here is a summary of what we discuss in inside this intersection and the starting of the section we
discussed about what is multilevel security, how it is different compared to authorizing the user at
the party level and what challenges we have that with that approach.
Eventually, we understand middle level security can provide you more flexibility, particularly for
non Web applications.
And if we have a requirement where you want to apply traditional rules at different layers of your application,
like repository service and controllers, we also looked at there are two ways our approaches to implement
metal level security.
One is invocation authorization, where we can control the execution of an materne or invocation of
a matter before and after by using pre authorized and post outrage.
And at the same time, we also looked at filtering authorization where we can control the execution
of a method based upon the parameters that is being received by the method and the parameters that is
being returned by the method using Prefill post filter.
Most importantly, please do remember, like if we are using post authorized and post filter, your
business logic defined inside your method will still be executed and the database, any interactions
that you have done will not be rolled back, even in the scenarios of four zero three exception being
thrown from the security framework.
With this, I'm hoping you're able to understand how to implement Matalote security inside any application.
I also upload the code that we have written inside the section to this video.
Please do some hands on inside the Web application that you are also building along with me.
And if you have any questions, you can look at the code that I'm being uploading.
And if you still have any questions, you can always reach out to me by posting your questions in the
Q&A section.
Thank you.
And see you in the next section by.