Consider referencing users by their Keycloak UUID in your application tables rather than maintaining a separate local user table. If your business requirements don’t demand querying users by name or other attributes locally, storing only the Keycloak UUID allows you to fetch full user details through the Keycloak Admin REST API (GET /realms/{realm}/users/{uuid}) as needed. This approach leverages Keycloak’s built-in IAM security, keeps your app decoupled from identity management concerns, and ensures you always have current data while minimizing local exposure of sensitive user info.