Let's try to recap what we have built in this section over the last five videos.
Firstly, the starting of the section, I walk you through the Easy Bank application and its associated
functionality.
And its a post that we also identified that this application may need six backend services in order
to serve its customers.
Once we identified all those backend services, we also built associated back in code by leveraging
risk control and implementing some static business logic, they always reconnect static response to
the consumers.
After that, we also validated all the six backend services with the default configurations provided
by the spring security and observed by default.
Spring security always tried to protect and secure all the services associated with the project.
Later on, we tried to customize.
As for our needs in the process, we created a new class with an annotation configuration which external
web security configure upper class and orating and retrofit all configure which accept S2P security
agreement.
We also went and look into the framework code what is the default code?
And we observed that by default, spring security tried to protect every request that is present in
the application.
We modified the code based upon our customer needs, where we have made for services as a secured one
and other two services are not secured by using an DEMETRIS.
We also discussed on how to deny all the requests using denial and permit all the requests using burm.
With these, we made some progress compared to the Section one and we know how to customize spring security
using and matches for my specific security implementation.
Also attaching the source code that we discussed with this video, please download the source code and
try to do some hensman by building some services, customizing ASPO requirement testing with a browser.
I, I'm very excited.
Starting next section.
Thank you.
By.