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

[Feature] custom API tools can use current user token for Authorization #12416

New Issue
Closed
opened 2026-02-21 19:07:19 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:07:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @lordk911 on GitHub (Mar 31, 2025).

Self Checks

  • 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

At present, when registering a custom tool, the token required for authentication needs to be configured in advance. It is hoped that the token of the current user can be filled in during the call (the user can enter the token at the start node or obtain a temporary token through the login action), because different users have different data rights. Custom tools may confirm the user's data access rights based on the token [
现在在注册自定义工具时，鉴权所需的 token 是需要提前配置的，希望能够在调用时填入当前用户的 token（用户可以在开始节点输入 token, 也可通过登录动作获取临时的 token）,因为不同的用户有不同的数据权限，自定义的工具可能会根据token确认用户的数据访问权限]

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @lordk911 on GitHub (Mar 31, 2025). ### Self Checks - [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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. At present, when registering a custom tool, the token required for authentication needs to be configured in advance. It is hoped that the token of the current user can be filled in during the call (the user can enter the token at the start node or obtain a temporary token through the login action), because different users have different data rights. Custom tools may confirm the user's data access rights based on the token [ 现在在注册自定义工具时，鉴权所需的 token 是需要提前配置的，希望能够在调用时填入当前用户的 token（用户可以在开始节点输入 token, 也可通过登录动作获取临时的 token）,因为不同的用户有不同的数据权限，自定义的工具可能会根据token确认用户的数据访问权限] ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🔨 feat:tools label 2026-02-21 19:07:19 -05:00
yindo closed this issue 2026-02-21 19:07:19 -05:00
yindo commented 2026-02-21 19:07:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 2, 2025):

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

Issue Summary:

  • Proposed feature enhancement for custom API tools to use the current user's token for authorization.
  • Aims to eliminate the need for pre-configured tokens.
  • Ensures data access rights are verified based on individual user tokens.
  • No activity or comments since the issue was opened.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If no updates are provided, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (May 2, 2025): Hi, @lordk911. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - Proposed feature enhancement for custom API tools to use the current user's token for authorization. - Aims to eliminate the need for pre-configured tokens. - Ensures data access rights are verified based on individual user tokens. - No activity or comments since the issue was opened. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If no updates are provided, the issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 🔨 feat:tools
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#12416
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?