Here's a situation I've been in more times than I'd like to admit. You set up Keycloak. It works great. Users register, log in, reset passwords — all handled. You move on to building the actual product. Then three weeks later, someone asks why the CRM doesn't have half the users in it. Or why the billing system is charging people who deleted their accounts six months ago. Or why the welcome email never went out. Because Keycloak knew. Nobody else did. So you go looking for the clean solution. Maybe you poll the admin API every few minutes? Sure, if you enjoy stale data and hammering your auth server for no reason. Maybe you query Keycloak's database directly? Works great until the next upgrade shuffles the schema and you spend a weekend figuring out why everything broke. Maybe you just... duplicate the registration logic in your backend and keep both in sync manually? I've seen this in production. It's exactly as bad as it sounds. None of these are good options.…