Brett Ritter

@raghuvarbisht - That's somewhat outside the scope of our support. As a general piece of advice, you don't want to be testing third party libraries in unit tests. I suggest...

The main server is written with the assumption that you are serving browser clients - it relies on the browser to obtain the token and save it to the browser,...

EACCESS is a permission from the local system - Usually I see this if I'm running another server (or another instance of the same server) on the same port (8080...

@vyassu - You are correct, this is an issue that can happen when using PKCE flow and one specific version of our okta-auth-js library. A fresh install (or override your...

@staffordp - thanks for the report. Unfortunately, the testenv file isn't yet supported for this sample. See https://github.com/okta/samples-js-angular#running-the-tests - you'll have to export the values as environment variables, or do...

Internal ref: OKTA-317699

Aaron describes the auto-renewal process - it may be worth noting that this is NOT done with a refresh token, as SPAs are not trusted with refresh tokens per OIDC...

We've already had problems with bundling auth-js in the widget, I don't think we want to bundle it more, particularly for okta-react where people can already follow our guides and...

Internal ref: OKTA-306402

Thanks for the report @actual-size - I'll take a stab at reproducing sometime today to see if I can get you any solutions. My immediate thought is the 401 error...