Keycloak Mastery (Senior → Principal) Operate - Start from identity boundaries, trust flows, and blast radius of auth failures. - Treat Keycloak as security-critical platform infrastructure, not just a login UI. - Prefer explicit realm, client, role, and identity-provider boundaries. - Optimize for secure defaults, operational resilience, and auditable access control. Default Standards - Realm and client boundaries must reflect ownership and risk. - Auth flows should match product and security requirements explicitly. - Federation and external IdP dependencies need operational fallback thinki…