Aaron Granick

This error/message will be thrown when calling `isAuthenticated()` and `autoRenew` is set to true and the session has expired. It should not cause any issue other than the noise in...

@koswedo I agree we should handle/hide this error better and not emit any "unhandled promise rejections". I've created an internal issue for this work: OKTA-439435 Thanks for bringing this to...

@jpspringall We have pushed a fix for this issue in `@okta/okta-auth-js` version `5.7.0`. If you are able, please confirm if updating to this version resolves your issue.

@ATud `handleLoginRedirect` may throw/reject. Try adding a `.catch()` block: ``` handleLoginRedirect().catch(e => { console.error(e); }); ``` If there is a real error (such as user not assigned to the application),...

@atud @andyrichardson @stevenmckinnon We have released a fix for this issue. After upgrading to `@okta/okta-react` [version 5.1.1](https://github.com/okta/okta-react/releases/tag/okta-react-5.1.1) you should see OAuth callback errors caught and displayed in the `LoginCallback` component....

@g-viet `parseFromUrl` does remove the `code`, `state` and other OAuth parameters from the URL after processing. Generally, the next step after this method is complete is to redirect, either to...

@BenPiggot The latest version of `okta-auth-js` should be compatible with the latest version of `okta-react`. We also have a react sample that may help: https://github.com/okta/samples-js-react

@johanerikssontrustly Thanks for the feedback. We will remove `token.value` in an upcoming version. Internal ref: OKTA-338251

@darkowic Do you know why the idToken is so large? Does it include a lot of custom scopes / data? Also I'm curious why you need to use cookie storage....

@stephen-dirtcreative thank you for bringing this use case to our attention. I've put up a new PR #1220 which should handle the case you describe. You are correct that we...