From 476c86c4f78328e53cf7ff668c8733c6f31f27b3 Mon Sep 17 00:00:00 2001 From: Kohei Tamura Date: Tue, 23 Jul 2019 16:31:06 +0900 Subject: [PATCH] Fix incorrect label name --- server_admin/topics/sessions/offline.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server_admin/topics/sessions/offline.adoc b/server_admin/topics/sessions/offline.adoc index 07cc25ada3..58142cb6a8 100644 --- a/server_admin/topics/sessions/offline.adoc +++ b/server_admin/topics/sessions/offline.adoc @@ -13,7 +13,7 @@ Your application is responsible for persisting the offline token in some storage The difference between a classic Refresh token and an Offline token is, that an offline token will never expire by default and is not subject of `SSO Session Idle timeout` and `SSO Session Max lifespan` . The offline token is valid even after a user logout or server restart. However by default you do need to use the offline token for a refresh token action at least once per 30 days (this value, `Offline Session Idle timeout`, can be changed in the administration console in the `Tokens` tab under `Realm Settings`). -Moreover, if you enable the option `Offline Session Max Limited`, then the offline token expires after 60 days regardless of using the offline token for a refresh token action (this value, `Offline Session Max lifespan`, can also be changed in the administration console in the Tokens tab under Realm Settings). +Moreover, if you enable the option `Offline Session Max Limited`, then the offline token expires after 60 days regardless of using the offline token for a refresh token action (this value, `Offline Session Max`, can also be changed in the administration console in the Tokens tab under Realm Settings). Also if you enable the option `Revoke refresh tokens`, then each offline token can be used just once. So after refresh, you always need to store the new offline token from refresh response into your DB instead of the previous one.