Aaron Granick

@WeipingGan That is certainly a strange issue! One thought I have is that it may be another application in another tab which is served on the same domain and is...

@kevinklitzke Thanks for the inquiry. The SDK supports both "up front" and "on demand" approaches to handling login remediations: https://github.com/okta/okta-auth-js/blob/master/docs/idx.md#up-front-approach It sounds like what you are describing can be handled...

@rwev Thank you for this great suggestion! Obviously, malicious code which has gained access to your `oktaAuthService` instance could do many, many bad things. For a secure web application, this...

@jakehockey10 `okta-auth-js` does not currently support self service registration, although this will be supported in an upcoming version. The signin widget is hitting the api directly, hopefully these links can...

To receive username and email you should add "email" and "profile" to the list of scopes, as shown here: https://github.com/okta/samples-js-vue/blob/master/okta-hosted-login/src/config.js#L8 The values will be available as properties of the "claims"...

@brvaland I would recommend setting `tokenManager.autoRenew` and `tokenManager.autoRemove` to `false` in [the tokenManager options](https://github.com/okta/okta-auth-js#autorenew) and then subscribing to the `expired` [event from the TokenManager](https://github.com/okta/okta-auth-js#tokenmanageronevent-callback-context). Your event handler can choose whether...

Add workaround for OKTA-509099 https://user-images.githubusercontent.com/47947204/177840087-77c4522a-54b2-40dd-9c86-e0e2d8a87846.mov

@jberube We will investigate this issue. In the meantime, you may be able to work around this by setting `autoRenew` option to false. You can listen to the 'expired' event...

internal ref: OKTA-379204