From aef2af4b936fb0c9313e67fcc49cf149fc41358f Mon Sep 17 00:00:00 2001 From: mikelgo Date: Thu, 9 Sep 2021 13:20:21 +0200 Subject: [PATCH] docs: fix broken link in silent-refresh documentation pointing to token-refresh --- docs-src/silent-refresh.md | 2 +- docs-src/summary.json | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/docs-src/silent-refresh.md b/docs-src/silent-refresh.md index 1621208e..3c232a3c 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.md) 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.html) 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. diff --git a/docs-src/summary.json b/docs-src/summary.json index 5bd2af3b..454bd44e 100644 --- a/docs-src/summary.json +++ b/docs-src/summary.json @@ -15,7 +15,10 @@ "title": "Silent Refresh", "file": "silent-refresh.md" }, - + { + "title": "Token Refresh", + "file": "token-refresh.md" + }, { "title": "Working with HttpInterceptors", "file": "interceptors.md"