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

The Problem Of The Dynamic Token Transmission Solution #14138

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

Originally created by @chuanqia on GitHub (May 23, 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.

In a local area network environment, we have embedded the Agent into the system page. The Agent has the capability to call the MCP API. At present, we need to set permissions for different users' access to the API interface, and thus we need to obtain a token. However, we currently have not found a way to dynamically pass in the token. So, is it possible to add a "dify" to receive path parameters, or adopt any other method to achieve the same effect?

Image

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 @chuanqia on GitHub (May 23, 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. In a local area network environment, we have embedded the Agent into the system page. The Agent has the capability to call the MCP API. At present, we need to set permissions for different users' access to the API interface, and thus we need to obtain a token. However, we currently have not found a way to dynamically pass in the token. So, is it possible to add a "dify" to receive path parameters, or adopt any other method to achieve the same effect? ![Image](https://github.com/user-attachments/assets/a998b029-beea-4c51-a7ec-e02506f28dae) ### 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:agent label 2026-02-21 19:15:44 -05:00
yindo closed this issue 2026-02-21 19:15:44 -05:00
yindo commented 2026-02-21 19:15:45 -05:00
Author
Owner
Copy Link
Copy Source

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

Based on the information available, Dify currently manages API tokens using a combination of the TokenManager and ApiToken classes, which handle token generation, storage, and validation. Token validation for API access is typically performed by checking the Authorization header for a Bearer token in incoming requests, as seen in the validate_and_get_api_token function. This means that the standard and supported way to transmit tokens dynamically is via the HTTP Authorization header, not as a path parameter or query parameter [source].

For embedded scenarios (such as with the chatbot), the token is expected to be provided in the configuration before the script is loaded, and it is then included in the requests made by the embedded component [source].

There is no evidence in the codebase or documentation that Dify currently supports passing tokens as path parameters, nor are there existing issues or discussions about enabling this feature. The recommended and secure approach is to use the Authorization header for dynamic token transmission.

If your use case requires passing tokens in a different way (such as via path parameters), this would require custom changes to the API endpoints to accept and validate tokens from the path, which is not currently supported out of the box.

Summary of current options:

  • Pass the token dynamically in the Authorization: Bearer <token> header for API requests.
  • For embedded widgets, ensure the token is set in the configuration before loading the script.

If you need a different mechanism (such as path parameters), it would require a feature request or custom modification to the Dify codebase. There are currently no built-in alternatives or workarounds documented for this scenario.

To continue talking to Dosu, mention @dosu-bot.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (May 23, 2025): <!-- Answer --> Based on the information available, Dify currently manages API tokens using a combination of the `TokenManager` and `ApiToken` classes, which handle token generation, storage, and validation. Token validation for API access is typically performed by checking the `Authorization` header for a Bearer token in incoming requests, as seen in the `validate_and_get_api_token` function. This means that the standard and supported way to transmit tokens dynamically is via the HTTP Authorization header, not as a path parameter or query parameter [[source]](https://github.com/langgenius/dify/blob/main/api/controllers/service_api/wraps.py). For embedded scenarios (such as with the chatbot), the token is expected to be provided in the configuration before the script is loaded, and it is then included in the requests made by the embedded component [[source]](https://github.com/langgenius/dify/blob/main/web/public/embed.js). There is no evidence in the codebase or documentation that Dify currently supports passing tokens as path parameters, nor are there existing issues or discussions about enabling this feature. The recommended and secure approach is to use the Authorization header for dynamic token transmission. If your use case requires passing tokens in a different way (such as via path parameters), this would require custom changes to the API endpoints to accept and validate tokens from the path, which is not currently supported out of the box. **Summary of current options:** - Pass the token dynamically in the `Authorization: Bearer <token>` header for API requests. - For embedded widgets, ensure the token is set in the configuration before loading the script. If you need a different mechanism (such as path parameters), it would require a feature request or custom modification to the Dify codebase. There are currently no built-in alternatives or workarounds documented for this scenario. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://go.dosu.dev/dosubot), mention @dosu-bot.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/a2403edc-0c56-4aa6-ab40-5fa511fcbe55?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/a2403edc-0c56-4aa6-ab40-5fa511fcbe55?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/a2403edc-0c56-4aa6-ab40-5fa511fcbe55?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/a2403edc-0c56-4aa6-ab40-5fa511fcbe55?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a2403edc-0c56-4aa6-ab40-5fa511fcbe55?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/a2403edc-0c56-4aa6-ab40-5fa511fcbe55?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a2403edc-0c56-4aa6-ab40-5fa511fcbe55?feedback_type=other)</sup>
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:agent
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#14138
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?