Why I Chose Keycloak

📖 Introduction

Modern applications require much more than a simple login page. As soon as multiple users, protected content, and different permission levels become part of the application, identity management turns into a core architectural component.

When I started building this platform, I had to decide whether to develop my own authentication system or rely on an established solution. After evaluating several options, I chose Keycloak.

Instead of reinventing authentication from scratch, I wanted to build the platform itself.

🚀 Authentication Is More Than a Login Form

Many developers think authentication simply means checking a username and password.

In reality, a production-ready authentication system includes far more:

• 🔑 Secure user authentication

• 👥 Role-based authorization

• 🛡️ Access control

• 🔄 Session management

• 🎫 JWT token handling

• 🔒 Password policies

• 🌍 Single Sign-On (SSO)

• 🔗 OAuth2 & OpenID Connect

• 📈 Scalability for future growth

Building all of this yourself is possible—but it quickly becomes one of the most complex parts of an application.

⚖️ Why I Didn't Build It Myself

Technically, I could have implemented my own authentication system.

However, authentication is not the feature that makes this platform unique.

Instead of maintaining thousands of lines of security-related code, I wanted to invest my time in building new features, writing content, and continuously improving the platform.

Using an established open-source solution significantly reduces maintenance while increasing security.

After comparing different identity providers, Keycloak became the clear choice.

It provides enterprise-grade identity and access management while remaining completely open source.

Keycloak includes:

• ✅ OAuth2

• ✅ OpenID Connect

• ✅ JWT Tokens

• ✅ Role-Based Access Control

• ✅ User Management

• ✅ Identity Federation

• ✅ Password Policies

• ✅ Session Management

• ✅ Multi-Factor Authentication

• ✅ Single Sign-On

Because Keycloak is designed for enterprise environments, it integrates perfectly into a modern Docker-based architecture.

🏗️ My Authentication Architecture

One design decision is especially important:

Angular never communicates directly with Keycloak.

Instead, the complete authentication flow is managed by the backend.

This approach keeps every security-sensitive operation on the server.

The frontend never needs to know how authentication actually works.

⚙️ Why I Prefer This Architecture

For me, this architecture offers several important advantages.

🔒 Better Security

The frontend never talks directly to the identity provider.

All authentication logic remains inside the backend.

🎯 Centralized Authentication

Spring Boot controls the complete login process.

This creates a single place where authentication and authorization can be managed consistently.

🧹 Cleaner Frontend

Angular only focuses on presenting the user interface.

Authentication logic stays out of the client application.

📈 Easier Maintenance

Because responsibilities are clearly separated, every component can evolve independently without affecting the rest of the platform.

🧩 Clear Responsibilities

Every technology in the platform has exactly one responsibility.

This separation makes the overall architecture easier to understand, test, and maintain.

🌱 Built to Scale

One of my main goals was creating a platform that can grow over time.

Instead of coupling every feature together, each component has a clearly defined responsibility.

That makes it much easier to introduce new services, extend existing functionality, or replace individual technologies without redesigning the entire application.

💡 Why Open Source Matters

Another reason for choosing Keycloak is the open-source ecosystem.

It is actively maintained, well documented, and widely adopted in enterprise environments.

Using proven open-source technologies allows me to focus on innovation instead of rebuilding existing solutions.

🎬 Related Video

In this video, I explain why I chose Keycloak for authentication and authorization in my platform. You'll see how it integrates with Spring Boot and Angular, why the backend manages the authentication flow, and how this architecture creates a secure, scalable, and maintainable foundation for modern web applications.

🎯 Conclusion

Keycloak has become a central part of my software architecture.

Combined with Spring Boot, Angular, PostgreSQL, Contentful, Docker, and Jenkins, it creates a modern platform where every component has a clear responsibility.

Rather than spending time building authentication from scratch, I can focus on what really matters:

• 🚀 Developing new features

• 📚 Creating valuable content

• 🔒 Keeping the platform secure

• 📈 Building a scalable architecture for the future

To me, that's what modern software engineering is all about—choosing the right tools, defining clear responsibilities, and building systems that are designed to evolve.