-
Notifications
You must be signed in to change notification settings - Fork 67
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
Question [Security]: using AsyncStorage to store token #62
Comments
One good option IMO is to use: https://github.com/oblador/react-native-keychain |
Hi @oferRounds
|
Yes, you are right - I referenced it as related to storing token on a client in general, in an unencrypted way |
In contrary Anyway it is recommended to use something like Thanks for pointing this out! |
Got you @vmurin, good to learn this info about the And thanks for always welcoming the feedback! |
I read the discussion, and I think I will switch from AsyncStorage to Keychain, but I am concerned about performance. Is Keychain's performance similar to Async Storage? |
I did't googled for performance comparison between AsyncStorage and Keychain. But I suppose the performance in this case is not an issue. All network response times during auth process are much bigger. |
Hi @vmurin
I see that the library is using AsyncStorage to store to the token, and was wondering, as AsyncStorage does not store data in a secure way, is this a problem?
Was reading this lately: richardkotze.com/coding/send-jwt-client-apollo-graphql#securely-storing-jwt-tokens
The text was updated successfully, but these errors were encountered: