[Refactor/Chore] Update how we save WebAppAccessToken #21642

Open
opened 2026-02-21 20:13:39 -05:00 by yindo · 1 comment
Owner

Originally created by @hyoban on GitHub (Jan 14, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Description

Follow up

We should not save the WebAppAccessToken in local storage

Motivation

No response

Additional Context

No response

Originally created by @hyoban on GitHub (Jan 14, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for refactors or chores; if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Description Follow up - #30977 - https://github.com/langgenius/dify/pull/30654#issuecomment-3736787978 We should not save the `WebAppAccessToken` in local storage ### Motivation _No response_ ### Additional Context _No response_
yindo added the stalestatus: blocked labels 2026-02-21 20:13:39 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Feb 15, 2026):

Hi, @hyoban. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You suggested refactoring the WebAppAccessToken storage to remove it from local storage for better security or architecture.
  • This idea builds on previous discussions and pull requests but hasn't seen further comments or activity recently.
  • No alternative solutions or updates have been proposed since your initial suggestion.
  • The issue remains unresolved and open for maintainers to review.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here.
  • If I don’t hear back within 15 days, I will automatically close this issue.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 15, 2026): Hi, @hyoban. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You suggested refactoring the WebAppAccessToken storage to remove it from local storage for better security or architecture. - This idea builds on previous discussions and pull requests but hasn't seen further comments or activity recently. - No alternative solutions or updates have been proposed since your initial suggestion. - The issue remains unresolved and open for maintainers to review. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here. - If I don’t hear back within 15 days, I will automatically close this issue. Thanks for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21642