langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Using HTTP request in workflow, Authorization API Key is displayed in plain text on the user side, which is unacceptable #2914

New Issue
Closed
opened 2026-02-21 17:51:34 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:51:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiaoxuan220 on GitHub (May 4, 2024).

Originally assigned to: @Yeuoly on GitHub.

Self Checks

  • This is only for bug report, if you would like to ask a quesion, 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 (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.6.5

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When building a workflow, if the Authorization API Key in HTTP is called, it will be displayed in plain text on the user side, which I think is unsafe
issue

✔️ Expected Behavior

Encrypt or do not display this option

❌ Actual Behavior

issue

Originally created by @xiaoxuan220 on GitHub (May 4, 2024). Originally assigned to: @Yeuoly on GitHub. ### Self Checks - [X] This is only for bug report, if you would like to ask a quesion, 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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### Dify version 0.6.5 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When building a workflow, if the Authorization API Key in HTTP is called, it will be displayed in plain text on the user side, which I think is unsafe ![issue](https://github.com/langgenius/dify/assets/22339743/c690194c-687d-45c8-bd5b-43215b21e032) ### ✔️ Expected Behavior Encrypt or do not display this option ### ❌ Actual Behavior ![issue](https://github.com/langgenius/dify/assets/22339743/bc88d14b-9b43-4417-aa50-a78e9ad1bc5c)
yindo added the 🐞 bug label 2026-02-21 17:51:34 -05:00
yindo closed this issue 2026-02-21 17:51:34 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#2914
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?