diff --git a/docs/additional-documentation/refreshing-a-token.html b/docs/additional-documentation/refreshing-a-token.html index 80bde46f..4e0690bc 100644 --- a/docs/additional-documentation/refreshing-a-token.html +++ b/docs/additional-documentation/refreshing-a-token.html @@ -51,8 +51,8 @@

Refreshing a Token using Code Flow (not Implicit Flow!)

When using code flow, you can get an refresh_token. While the original standard DOES NOT allow this for SPAs, the mentioned OAuth 2.0 Security Best Current Practice document proposes to ease this limitation. However, it specifies a list of requirements one should take care about before using refresh_tokens. Please make sure you respect those requirements.

Please also note, that you have to request the offline_access scope to get an refresh token.

-

To refresh your token, just call the refresh method:

-
this.oauthService.refresh();

Automatically refreshing a token when/ before it expires (Code Flow and Implicit Flow)

+

To refresh your token, just call the refreshToken method:

+
this.oauthService.refreshToken();

Automatically refreshing a token when/ before it expires (Code Flow and Implicit Flow)

To automatically refresh a token when/ some time before it expires, just call the following method after configuring the OAuthService:

this.oauthService.setupAutomaticSilentRefresh();

By default, this event is fired after 75% of the token's life time is over. You can adjust this factor by setting the property timeoutFactor to a value between 0 and 1. For instance, 0.5 means, that the event is fired after half of the life time is over and 0.33 triggers the event after a third.

diff --git a/docs/changelog.html b/docs/changelog.html index 1f661ab0..b76edf64 100644 --- a/docs/changelog.html +++ b/docs/changelog.html @@ -37,17 +37,10 @@

9.2.0 (2020-03-28)

Features

Bug Fixes