This repository has been archived by the owner on Oct 24, 2024. It is now read-only.
feat: handle onSessionExpired, add isAuthenticated option #648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a default handler for
onSessionExpired
Adds a new option
isAuthenticated
which works withonAuthRequired
Also:
postLogoutRedirectUri
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently failure while auto-renewing a token will emit an "error" event from the okta-auth-js internal TokenManager. This behavior is unchanged, however TokenManager was not exposed by this SDK, nor was this behavior documented, so it was previously very difficult or impossible to listen for this event using this SDK. If the session has expired, the user will need to reload the page to re-enter login flow.
Issue Number: 257120
What is the new behavior?
A default handler is added for
onSessionExpired
(option was added in[email protected]
)This is called in the case of session is expired or was closed outside the application. Currently this will only be detected if there is failure to renew
accessToken
whenautoRenew
is true.Does this PR introduce a breaking change?
(see notes above. I consider unhandled session expiration to be a bug. If a customer was accessing the TokenManager and listening to the event (as a workaround) they no longer need to do this)
Other information
Reviewers