In the first part we setup a local Keycloak instance. In this blog we will see how we can leverage Keycloak to secure our frontend. For this purpose we will create a small Spring Boot application that will serve a webpage. The next and last blog will show how authentication can be used between services.
As mentioned we will create a small Spring Boot microservice and secure it using Spring Security and Keycloak. The service that we will create in this blog is the "frontend" Spring Service. It serves a simple web page that displays a hello message including the users email adres as registered in Keycloak. The next blog we will build the service and propagate the authorization from to frontend to service we cal. This way we build a complete Single Sign-On solution.
Continue reading →
These days companies gather and manage vast amounts of user data.
Loss of this data will expose companies to financial/legal liabilities or damages to their brand.
This is because over the last years, governments have introduced new regulations like the General Data Protection Regulation (GDPR).
Because of this, security is a major cross-cutting concern for application architecture.
This two-part blog post explains how you can leverage Keycloak to secure your Spring microservices.
The first blog will focus on how to install and configure Keycloak.
The second blog will show how to use Keycloak to secure your Spring Boot microservices.
Keycloak is a modern open source Identity and Access Management solution.
It enables us to secure all sorts of frontend applications (apps) / services and offers the following features:
A corporate version, known as Red Hat Single Sign-On (SSO), is also available from (and supported by) Redhat.
The support and the ability to connect to existing identity systems make it a good fit for large organisations.
Continue reading →
Congratulations! Someone has made the wise decision to hire you as the new technical lead.
It is an exciting time.
You start in a new environment, will be working with a new team and maybe even have to learn new technologies along the way.
This can be quite challenging.
In the first article I wrote about introducing change.
In this second article I want to share my personal views on shaping great teams.
As team lead, there are certain values that are just part of me and they way I think about leadership.
Fortunately, in JDriven I found a company that matches my values step by step.
These values are #commit, #develop and #share.
In this article I want to go into some of the values that I consider important to create a great team.
I consider sharing knowledge one of the most important values.
Teams consist of people with different experience levels and backgrounds.
It should be everyone’s goal to help each other grow and develop.
You can share knowledge in many ways.
Some examples are pair programming, help troubleshooting/debugging, collaborate on a design or technical sessions or writing articles.
By doing this we grow as a team.
Where one gains technical skills the other gains leadership skills or new insights.
Also don’t forget that even experienced architects can learn about new technologies from new programmers.
Asking for help from others also shows that you’re not some all knowing dictator and one man team.
Working on complex projects is a team effort that benefits from actively helping each other.
Continue reading →
Congratulations! Someone has made the wise decision to hire you as the new technical lead.
It is an exciting time.
You start in a new environment, will be working with a new team and maybe even have to learn new technologies along the way.
This can be quite challenging.
In this two-part article I want to share my personal views regarding Introducing change and shaping teams as a technical lead.
When starting in this new environment you probably bring lots of energy and want to leverage your experience to change things for the better.
In my opinion introducing changes in a new environment requires some consideration.
Continue reading →
