okta-auth-js icon indicating copy to clipboard operation
okta-auth-js copied to clipboard

The official js wrapper around Okta's auth API

Results 169 okta-auth-js issues
Sort by recently updated
recently updated
newest added

Hello We have an Angular app using "@okta/okta-signin-widget": "version": "5.12.0", with this configuration ``` { redirectUri: window.location.origin + environment.authorizationCallbackUri, authParams: { issuer: environment.oktaServer + '/oauth2/default', pkce: true, responseType: ['code'], responseMode:...

Hi everyone, maybe you are experiencing same, or maybe you experienced same, but I would love to share with you our current experience with MFA ### Cookies - other sites...

From the docs: > If an authorization code is present, **it will be exchanged for token(s)** by posting to the tokenUrl endpoint. https://github.com/okta/okta-auth-js#tokenparsefromurloptions However this isn't the case. The promise...

Changes in [this PR](https://github.com/okta/okta-auth-js/pull/907) were made to `generated` instead of `templates`. And were lost after [regenerating samples](https://github.com/okta/okta-auth-js/pull/949) This PR restores changes to `templates` and `generated`

While running Cypress tests with Okta Authentication, after successfully mocking logging in or implementing Okta Authentication according to Cypress documentation, the token in localStorage gets overwritten to `{}` - which...

There looks to be 2 ways of configuring token storage: Using the storageManager: ``` storageManager: { token: { storageType: 'sessionStorage', } } ``` Using token manager storage property: ``` tokenManager:...

feat: Updates Adds feature to store a device_secret in TokenStore Allows the TokenStore to store a device_secret in the TokenStore if the device_secret scope is requested. Allows the device_secret and...

Hi, I think this also relates to #890 I previously created an issue #592 explaining the use of cookies within in server side rendering, though the actual issue raised was...

I'm having trouble determining if allowing a user to sign up (not sign in) is possible through this library. The API reference doesn't seem to have a method for this....