You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/oidc-usage.md
+5-3
Original file line number
Diff line number
Diff line change
@@ -183,13 +183,15 @@ this is used for validating the JWT signature.
183
183
### Initialization
184
184
185
185
After constructing the manager with the proper settings, you MUST call the `manager.init()` function, which will do the following:
186
-
1. If the function has already been initialized (checked via the hasInit variable), it simply returns. This is because certain configurations and setups do not need, and should not be, repeated.
186
+
187
+
1. If the function has already been initialized (checked via the hasInit variable), it simply returns. This is because certain configurations and setups do not need to be repeated.
187
188
2. initialize the passed store (calls `OidcStore.init()`)
188
189
3. ensure that the discovery document has been retrieved (if the lazy constructor was used).
189
190
4. if the discovery document contains a `jwks_uri` adds it the to the keystore.
190
191
5. handle various state management tasks. It loads logout requests and state results (from samePage redirects), also attempts to load cached tokens if there are no state results or logout requests.
191
-
6. Starts Listening to incoming Front Channel Logout requests.
192
-
7. Starts listening to token expiry events for automatic refresh_token circulation.
192
+
6. If the loaded token has expired and a refresh token exists, it attempts to refresh it, otherwise the token will be removed form the store.
193
+
7. Starts Listening to incoming Front Channel Logout requests.
194
+
8. Starts listening to token expiry events for automatic `refresh_token` circulation.
0 commit comments