This weekend, I attended the WordCamp London 2018 and talked about the process to secure web applications based on WordPress.
After organising it last year and delivered a talk about getting started with plugin development, this year I’ve been to WordCamp Torino 2018 to talk about the process to secure web applications based on WordPress.
In 2000, the internationally renowned security technologist Bruce Schneier wrote: “Security is a process, not a product”. In the same essay, he wondered: “Will we ever learn?”. Apparently not.
How many times have you considered your WordPress application security only once completed? How many times have you installed a security plugin and thought it was enough? Securing a web application doesn’t mean installing a plugin just before deployment. Not at all.
I’m very passionate about security and I’d like to share my thoughts with you. My focus will be the security awareness related to web applications. Is WordPress secure? I will answer this question very clearly. And you’re not gonna like it!
Last Update: 3 March 2019
In this article, we’re going to secure a Spring Boot application using Keycloak.
Before doing that, let’s briefly recall what we have done so far.
First, we talked about the main features of Keycloak used in this series and learned how to install and boot the Keycloak server.
Then, we set Keycloak with some basic configurations to use it for securing a web application (providing it with authentication and authorization).
In this article, we’re going to learn how to:
- Create a client in Keycloak;
- Set up the Spring Boot application;
- Define the application resources;
- Add access policies based on user roles.
You can check out the full source code of the demo project we’re going to build on GitHub.
Let’s get started! Continue reading “Securing a Spring Boot Application with Keycloak”