Brett Ritter

@fuzzthink Actually, yes - We just got the patch into the upstream package (njwt has a 0.4.1 release) and this package is getting that and several other upstream updates as...

@riteshmaurya - Thanks for the report. This sounds very similar to https://github.com/okta/okta-oidc-js/issues/460 Per the comments there, can you install to the latest version (and make sure you end up with...

@riteshmaurya - Thanks - unfortunately, we can't see what version of auth-js this installed. You can look at the package.json of the file in `node_modules/@okta/okta-auth-js/` to see what version it...

@riteshmaurya - Thanks again, but we still need some more information to diagnose this: * True/false? - the user is not logging out or taking other actions while this screen...

@elyast - Thanks for the report. A handful of follow-up questions: * What are the scopes requested by your application? * When the user is in this state, and reloads...

Thanks @elyast - It looks like the issue is that the user's access token is expired, which is why the backend call fails. (that's expected) When you reload the page,...

@salazarm - thanks for the report. Short version: You are doing the recommended approach, but we are putting together a better recommendation for you, as recent changes have highlighted some...

@trentinthomas - Thanks for the report. Expired/invalid tokens are expected to be removed from localstorage. Tokens that remain valid are NOT expected to be removed. There may be a complication...

@trentinthomas - okta-react 3.0.3 is out on npm, let me know if that helps.

@d-gottlieb - Not so much "missed", as in a dependency. We have changes in the works in okta-auth-js, and then these changes need to be consumed by okta-react, so expect...