Recently, I worked on a custom Keycloak SPI to connect authentication events with our application workflow. One interesting part of the implementation was handling account lockout events — not by changing Keycloak's core, but by extending it through an Event Listener SPI. I put together this short carousel to share: 🔹 The problem 🔹 The approach I took 🔹 How the integration works 🔹 What I learned from building it My biggest takeaway: Good engineering isn't always about changing the platform — sometimes it's about extending it in the right way. If you're working with Keycloak, Java, or backend security, I'd love to hear about your experience. #Keycloak (https://www.linkedin.com/search/results/all/?keywords=%23keycloak&origin=HASH_TAG_FROM_FEED) #Java (https://www.linkedin.com/search/results/all/?keywords=%23java&origin=HASH_TAG_FROM_FEED) #BackendDevelopment (https://www.linkedin.com/search/results/all/?keywords=%23backenddevelopment&origin=HASH_TAG_FROM_FEED) #Authentication (https://www.linkedin.com/search/results/all/?keywords=%23authentication&origin=HASH_TAG_FROM_FEED) #SoftwareEngineering (https://www.linkedin.com/search/results/all/?keywords=%23softwareengineering&origin=HASH_TAG_FROM_FEED)

Mrityunjay Thakur

Java Backend Developer | Spring Boot & Microservices