title: Bring the Resource Server to refresh tokens?
body: <p>I have the following scenario in which the Resource Server is given an access token as well as a refresh token while requesting a resource (in my case a REST API).</p>
  
  <p>The Authentication Server is a remote server, so I have implemented the Resource Server by using RemoteTokenServices and @EnableResourceServer.</p>
  
  <p><a href="https://i.stack.imgur.com/s1ih9.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/s1ih9.png" alt="enter image description here"></a></p>
  
  <p><strong>The scenario works like this</strong>: the user goes to a login form and provides its username and password. The Client validates the credentails with the Auth Server and when successful it saves a cookie in the user browser with the access and refresh token.</p>
  
  <p>Now the User goes to another subdomain (technically accessing another application) and is expected to be recognized. </p>
  
  <p>The Client and the Resource Server do not have any communication links. </p>
  
  <p>I am aware that it is not best practice to have the refresh token leave the client. </p>
  
  <p><strong>Now my question:</strong> since I already have the refresh token, I would like to extend the functionality of my application by allowing the RS to refresh tokens as well. I know that according to the OAuth2 specification, this is not the role of the RS. Does it mean I need to implement the Client? If yes, how do I do that? </p>