Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config storageProvider #425

Open
robsoden opened this issue Jun 14, 2024 · 0 comments
Open

config storageProvider #425

robsoden opened this issue Jun 14, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@robsoden
Copy link

Describe the feature request?

The okta-auth-js package allows for the configuration of a custom storageProvider in the case where cookies or browser storage are not available or not desired.

In react native, those browser-based options don't exist. However, the config is missing the ability to configure an alternate storageProvider.

If one uses the custom-sign-in path, it's unclear where (or if) the access and refresh tokens are being stored. We also end up with warnings such as "This browser doesn't support localStorage. Switching to sessionStorage" which can't be suppressed. As a result, it's unclear if it's even possible to use refreshTokens with this library.

It would be ideal to have the same config option for storageProvider so we could access and use these tokens, via state management (redux, etc) or AsyncStorage.

New or Affected Resource(s)

refresh tokens, token storage

Provide a documentation link

No response

Additional Information?

If it is possible to use refresh tokens with this library, it would be ideal to add an example to the documentation that explicitly explains where the tokens are being stored.

@robsoden robsoden added the enhancement New feature or request label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant