opened
BaHXeLiSiHg
username_0
Have latest IdentityServer4 with configured refresh token flow for client:

```
...
AllowOfflineAccess = true
UpdateAccessTokenClaimsOnRefresh = true,
AccessTokenLifetime = 120,
RefreshTokenUsage = TokenUsage.OneTimeOnly,
RefreshTokenExpiration = TokenExpiration.Absolute,
AbsoluteRefreshTokenLifetime = 300
...
```

Wanted to test it in short period of time, to ensure that everything works. Refresh token requesting every 60 seconds (half of access token lifetime), but at 5-th refresh token request (300 seconds) getting error that refresh token expired.

I expected that every new refresh token will have fresh expire time (300 seconds), but seems like even when i get new refresh tokens every time, they have inherited expiration time from first-issued refresh token.

Am i doing something wrong?

![image](https://user-images.githubusercontent.com/15612158/109274984-ca193880-781c-11eb-9008-d2ce51f0c141.png)
![image](https://user-images.githubusercontent.com/15612158/109275103-f59c2300-781c-11eb-8eca-abc2251d3934.png)
![image](https://user-images.githubusercontent.com/15612158/109275212-195f6900-781d-11eb-88d2-8e3dfb3a3d2a.png)
Fresh issued refresh token expired
issue
created
BaHXeLiSiHg
username_0
Just encountered post [https://karatejb.blogspot.com/2019/09/aspnet-core-identity-server-4-refresh.html](url) that explained little bit detailed refresh token behavior.

So next configuration did the trick:

```
...
AllowOfflineAccess = true
UpdateAccessTokenClaimsOnRefresh = true,
AccessTokenLifetime = 120,
RefreshTokenUsage = TokenUsage.OneTimeOnly,
RefreshTokenExpiration = TokenExpiration.Sliding,
SlidingRefreshTokenLifetime = 300,
AbsoluteRefreshTokenLifetime = 0
...
```
comment
closed
BaHXeLiSiHg
username_0
issue