title: SignalR Core authorization with refreshing token
body: <p>I have a couple of questions regarding SignalR Core authorization on the server side;</p>
  
  <p>My server is written in ASP.NET Core, and it uses SignalR CORE for sending notifications to users.</p>
  
  <p>1) If a client has connected with an options object containing an AccessTokenProvider and the access token changes -- does the server re-authorize the user even when using a long-running connection like a socket? Ie does SignalR create a new User object on the server side when the client's access token changes, while a connection is alive? If not -- how should this be handled?</p>
  
  <p>2) On the client side - if a connection is aborted either from server side or by the client requesting a stop, does DisposeAsync() have to be called and a new connection object created, or can the previous one be reused safely without disposing it?</p>
  
  <p>Thanks.</p>