ESEN

Contact

I reply within a day or two.

About
← Projects

devs · case study

Centralized identity and permissions for a financial company

Each app at a financial firm had its own login. We designed one identity and permissions platform for staff, customers and suppliers.

The problem

A financial company had internal, customer and supplier platforms, each with its own login. Thousands of users had one account per application, and each application handled permissions its own way.

How we solved it

We split two questions: who you are and what you can do.

For identity, Keycloak became the single front door for every platform; employees sign in with their Entra ID account. For permissions, we used the Zanzibar model, Google’s authorization system, implemented with SpiceDB: permissions are stored as relationships between users and resources, and each application asks the central service whether someone can do something instead of keeping its own rules. Everything runs on Azure, on AKS.

My role

It was my first project working side by side with a software architect. We defined the architecture and the tools together, and the two of us carried it out.

Result

It went into production and was handed over to the client: one front door and one permissions model for all its platforms.