Skip to content

Commit 2c56eef

Browse files
committed
graceful refresh token
1 parent 5b855c3 commit 2c56eef

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

en/includes/guides/fragments/manage-app/oidc-settings/refresh-token.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ By default, whenever the refresh token is exchanged for a new access token, {{pr
88
If you select the **Renew refresh token** option, each time the refresh token is exchanged for a new access token, {{product_name}} invalidates the existing refresh token and issues a new refresh token.
99

1010
{% if product_name == "Asgardeo" or (product_name == "WSO2 Identity Server" and is_version > "7.2.0" ) %}
11+
1112
#### Extend expiry time of renewed refresh token
1213

1314
!!! note
@@ -21,13 +22,13 @@ When you set this configuration to `false`, renewed refresh tokens carry the rem
2122
This option specifies the validity period of a refresh token in seconds. The default value is 86400 seconds.
2223

2324
{% if product_name == "Asgardeo" or (product_name == "WSO2 Identity Server" and is_version > "7.3.0") %}
25+
2426
#### Graceful refresh token rotation
2527

2628
!!! note
2729
This option is only applicable when **Renew refresh token** is enabled.
2830

29-
When **Renew refresh token** is enabled, a client that never received the newly issued refresh token (for example, due to a dropped network connection) would normally be forced to re-authenticate. Enabling **Graceful refresh token rotation** lets the previous refresh token remain usable for a short, configurable grace window after it has been rotated, so the client can recover without interrupting the user session.
30-
31+
When **Renew refresh token** is enabled, if a client never receives the newly issued refresh token (for example, due to a dropped network connection), the server forces the client to re-authenticate. Enabling **Graceful refresh token rotation** lets the previous refresh token remain usable for a short, configurable grace window after rotation, so the client can recover without interrupting the user session.
3132

3233
#### Graceful refresh token rotation validity period
3334

@@ -60,9 +61,9 @@ The maximum allowed reuse limit on Asgardeo is **5**.
6061

6162
The following runtime rules apply during the grace window:
6263

63-
- **Replay inside the grace window .** If the client replays the old refresh token (RT0) inside the grace window, {{product_name}} issues a new access token and a new refresh token, and revokes the previously issued rotated token (RT1). Only one child of the parent token is honoured at a time; the most recent replay always wins.
64+
- **Replay inside the grace window.** If the client replays the old refresh token (RT0, the original token) inside the grace window, {{product_name}} issues a new access token and a new refresh token, and revokes the previously issued rotated token (RT1, the replacement token). Only one child of the parent token is honoured at a time; the most recent replay always wins.
6465
- **Using the new refresh token closes the grace window.** Once the client successfully uses the rotated token (RT1), the previous gracefully-rotated token (RT0) is immediately revoked. Any subsequent attempt to replay RT0 returns `400 invalid_grant`.
6566
- **Reuse limit.** If the old refresh token is replayed more times than the configured limit within the window, further replays return `400 invalid_grant`.
6667
- **Grace window expiry.** If the old refresh token is replayed after the validity period has elapsed, the request returns `400 invalid_grant`.
6768

68-
{% endif %}
69+
{% endif %}

0 commit comments

Comments
 (0)