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

Updating Token #515

Open
anthhub opened this issue Oct 24, 2024 · 2 comments
Open

Updating Token #515

anthhub opened this issue Oct 24, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@anthhub
Copy link

anthhub commented Oct 24, 2024

Is your feature request related to a problem? Please describe.

doc The documentation mentions using the updateToken method to update a token in "local secure storage." However, the specific location or nature of this storage is unclear. Additionally, I need clarification on whether it is secure enough to store sensitive information.

Describe the solution you'd like

I'd like a detailed explanation of what "local secure storage" refers to in this context. Is it a specific storage location within the device or app environment (e.g., secure keychain, encrypted local storage)? Additionally, I would like to know the security measures in place and if it is recommended to store sensitive information like authentication tokens or personal data in this storage.

Describe alternatives you've considered

One possible alternative would be to use other secure storage methods such as encrypted databases or server-side token management, depending on the sensitivity of the data.

Additional context

Please include additional information in the documentation on how "local secure storage" works within the Telegram Mini Apps SDK, and the best practices for storing tokens securely.

@anthhub anthhub added the enhancement New feature or request label Oct 24, 2024
@anthhub
Copy link
Author

anthhub commented Oct 24, 2024

image

@heyqbnk
Copy link
Member

heyqbnk commented Dec 15, 2024

Unfortunately, there is no explanation on the Telegram's side. I assume, this is the encrypted storage you can't access without using some specific biometry data. I can also assume, that this value is stored only locally, so you can't access on the other device using the same Telegram account

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

2 participants