diff --git a/docs/additional-documentation/silent-refresh.html b/docs/additional-documentation/silent-refresh.html index 607299de..181ddf41 100644 --- a/docs/additional-documentation/silent-refresh.html +++ b/docs/additional-documentation/silent-refresh.html @@ -49,7 +49,7 @@
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 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 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.
To use this approach, setup a redirect uri for the silent refresh.
For this, you can set the property silentRefreshRedirectUri in the config object: