title: ADFS 3.0 using OAuth and Persistent Refresh Tokens
body: <p><strong>Question 1</strong></p>
  
  <p>We are currently using ADFS and OAuth (using Windows Server 2012 R2 with ADFS 3.0). Our test applications (both WPF and mobile apps) can successfully authenticate and get an Access Token and a Refresh Token. We can after that continue to use the Access Token until it expires and after that use the Refresh Token to get a new Access Token. 
  So far so good, but the problem is when the Refresh Token expires, we need to force the user to enter their credentials again. Our aim is to have the user to only enter their credentials once and then use a short lifetime for Access Token and a Persistent lifetime (or really really long) for Refresh Tokens. </p>
  
  <p>According to some blog posts when using a Refresh Token you should get a new Access Token and sometimes also a new Refresh Token, but in our case we never get a new refresh token, so that one eventually expires.</p>
  
  <p>Is this even possible using ADFS 3.0 and OAuth to have a persistent Refresh Token? or get new refresh tokens from time to time so that the user doesn't have to enter their credentials again? or is it possible to have a really long lifetime for refresh tokens.</p>
  
  <p><strong>Question 2</strong></p>
  
  <p>There is also a lot of different properties you can set in ADFS that we are not sure of </p>
  
  <ul>
  <li>TokenLifetime - This is the access token lifetime? what is maximum value?</li>
  <li>SsoTokenLifetime - This is the refresh token lifetime? what is maximum value?</li>
  <li>PersistentSsoLifetimeMins - what is this?</li>
  <li>PersistentSsoEnabled - I guess should be set to true to have refresh tokens working</li>
  </ul>