title: Is it possible to configure Keycloak to store the access-token/JWT as a Bearer Token instead of as a Cookie?
body: <p>My understanding (which may be incorrect) of Keycloak is that once an User has logged in and is authenticated, the access-token/JWT is then stored as a cookie in the browser (under the default name 'kc-access').</p>
  
  <p>Is it possible to configure keycloak to instead store the access-token directly as a Bearer Token instead of in a cookie?</p>
  
  <p>Asking as I wish to use Keycloak to secure a web application, however most resources I have read on Authentication usually talk about access-tokens stored as Bearer Tokens, rather than as cookies. </p>
  
  <p>From the Keycloak documentation, I cannot see any mention of options to store the access-token as a Cookie OR Bearer Token - Am I misunderstanding how Keycloak is meant to be used for providing authentication for web applications?</p>