title: jHipster, Keycloak - How to update user data on keycloak correctly?
body: <p>I'm trying to figure out the best method to exchange user information between a Spring application, and an Identity Provider.
  To be specific, it's an application generated with jHipster, using Keycloak as the IdP.</p>
  <p>The data exchange can be done easily with <a href="https://search.maven.org/search?q=a:keycloak-admin-client" rel="nofollow noreferrer">keycloak-admin-client</a>, the problem is that after the update, <em>the client still haves the same Access Token in memory</em>, basically it's not in sync with the new data sent to Keycloak.</p>
  <p>Do you know which is the best method to handle this situation?</p>
  <p>I tried to invalidate the current access token, in order to force the client app to ask for a new one using the refresh token. But apparently there's no way to do this with the admin-client (at least, I couldn't find it).</p>
  <p>At this point I don't see other options then asking for a new access token from client, once it sends an user data update request.</p>
  <p>It doesn't seem a proper solution to me, I feel like maybe there's a more &quot;elegant&quot; procedure for this situations.</p>
  <p>If you have any better solution, I'm all ears.</p>