 Hi, in this second screencast, I want to show you how you can combine Spring Security with C-Cloud. So, if we take back our application that we built in the first part here, the first thing I need to do is to add the Spring Security libraries. And I can do that easily by just providing the Spring Security starter dependencies. So, let me add it here, Spring Security. Okay, that will bring in all the needed jars to use Spring Security. And then, what I need to do is to add a security config class, like you will do with all Spring Security projects. And to do that, the easiest way to start is to go to the key cloud documentation. And in this documentation, we have documentation for all the adapters, including the Spring Security one. And here in the doc, you will see a code sample of a security config class. We can pretty much just copy this sample here and just paste it in our project. So, if we go here in this part here, I just paste that. I remove the public identifier here. And here, let me go through this class quickly. So, here we mentioned we have some configuration. That's an important one. We want to enable web security. So, the first method here, configure global. Here, as the method suggests, we can do some global configuration. We could keep the defaults, but in the default configuration, Spring Security will add a prefix to all our roles. So, imagine our user has the role user, it will prefix it with role in uppercase underscore user. So, we could change that on the key cloud side, but we can also easily change that in the global config and just tell Spring Security to not add any prefix. How do we do that? So, we just get an instance of our key cloud authentication provider here. And here we can set a pretty simple method, which is called setGrantedAuthoritiesMapper. And what we want is a simple authorityMapper. Then we just pass this class to our authentication provider, and that's it. Then, there's one more thing we need to add is where the Spring Security key cloud adapter will look up its configuration. By default, it will be looking for a file called keycloud.json. But, here we are dealing with a Spring Boot app, and we want to make use of the application.property cell. So, we can easily tell the adapter to look in the properties cells instead of looking for a keycloud.json file. So, let's create a new bin. And here, we simply inject a bin, which is called keycloud config resolver. And what we do here is we return a keycloud Spring Boot config resolver. This way, we are sure it will look at its config in the application.property. And then, while we have the configure method, you probably know that from your previous Spring Security project. And here, let's just change that to fit our example. So, here we are dealing with products, and we have the role user in lower case. So, that's all we need to do. And one last thing is if we go to our properties, we don't need any security constraints anymore, because it's Spring Security that handles that. Okay, so, I just save it, and I start again my app. And if I browse to my app, let's bring in here for it. Okay, I go to my products, and here I log in with Siby. Siby, I log in. And you see, it's just working. But this time, it's using Spring Security. Okay, so in the third part, we will divide our Spring app into two different apps, and we will see how we can secure the rest services with keycloud. Thank you very much.