okta-react-native icon indicating copy to clipboard operation
okta-react-native copied to clipboard

config storageProvider

Open robsoden opened this issue 8 months ago • 0 comments

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 avatar Jun 14 '24 12:06 robsoden