From 7e1482939692a7ae7bf31f960049c575b747e956 Mon Sep 17 00:00:00 2001 From: Christoph Date: Mon, 8 Jan 2024 10:24:28 +0100 Subject: [PATCH] fix link --- docs-src/silent-refresh.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-src/silent-refresh.md b/docs-src/silent-refresh.md index 3c232a3c..1621208e 100644 --- a/docs-src/silent-refresh.md +++ b/docs-src/silent-refresh.md @@ -1,6 +1,6 @@ ## Refreshing when using Implicit Flow (Implicit Flow and Code Flow) -**Notes for Code Flow**: You can also use this strategy for refreshing tokens when using code flow. However, please note, the strategy described within [Token Refresh](./token-refresh.html) is far easier in this case. +**Notes for Code Flow**: You can also use this strategy for refreshing tokens when using code flow. However, please note, the strategy described within [Token Refresh](./token-refresh.md) is far easier in this case. To refresh your tokens when using implicit flow you can use a silent refresh. This is a well-known solution that compensates the fact that implicit flow does not allow for issuing a refresh token. It uses a hidden iframe to get another token from the auth server. When the user is there still logged in (by using a cookie) it will respond without user interaction and provide new tokens.