langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[Bug] Missing Authentication UI for AWS Tools Plugin (Identity fields not rendered) #950

New Issue
Open
opened 2026-02-16 10:21:05 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:21:05 -05:00
Owner
Copy Link
Copy Source

Originally created by @ytnobody on GitHub (Jan 26, 2026).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues Dify issues & Dify Official Plugins, 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.

Dify version

Dify Cloud 1.11.4

Plugin version

AWS Tools (langgenius/aws_tools) v0.0.17

Cloud or Self Hosted

Cloud

Steps to reproduce

There is a critical discrepancy between the manifest.yaml and the Dify Cloud UI. Although the manifest defines identity fields for AWS credentials (Access Key ID, Secret Access Key, etc.), these fields are not rendered anywhere in the Dify Cloud interface, making it impossible to authenticate and use the plugin.

Steps to Reproduce

  1. Install the "AWS Tools" (langgenius/aws_tools) plugin on Dify Cloud.
  2. Attempt to configure the plugin or provide credentials.
  3. Observe that there are no input fields for aws_access_key_id or aws_secret_access_key, even though they are required by the plugin's schema.
  4. Running any node (e.g., AWS S3 Operator) results in an AccessDenied error because no credentials can be supplied.

Expected Behavior

The Plugin configuration page should display the identity input fields defined in the manifest.yaml so that users can provide their AWS credentials.

Actual Behavior

The configuration UI is empty or missing the credential input fields entirely, leading to unauthorized API calls.

Technical Evidence

In the plugin's manifest.yaml, the following identity fields are defined but not shown in the UI:

identity:
  aws_access_key_id:
    type: text-input
    required: true
  aws_secret_access_key:
    type: secret-input
    required: true
  aws_region:
    type: text-input
    required: true

Environment

  • Dify Cloud (SaaS)
  • Plugin: AWS Tools (langgenius/aws_tools) v0.0.17

✔️ Error log

No response

Originally created by @ytnobody on GitHub (Jan 26, 2026). ### Self Checks - [x] This is only for bug report, 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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. ### Dify version Dify Cloud 1.11.4 ### Plugin version AWS Tools (langgenius/aws_tools) v0.0.17 ### Cloud or Self Hosted Cloud ### Steps to reproduce There is a critical discrepancy between the `manifest.yaml` and the Dify Cloud UI. Although the manifest defines `identity` fields for AWS credentials (Access Key ID, Secret Access Key, etc.), these fields are not rendered anywhere in the Dify Cloud interface, making it impossible to authenticate and use the plugin. ### Steps to Reproduce 1. Install the "AWS Tools" (langgenius/aws_tools) plugin on Dify Cloud. 2. Attempt to configure the plugin or provide credentials. 3. Observe that there are no input fields for `aws_access_key_id` or `aws_secret_access_key`, even though they are required by the plugin's schema. 4. Running any node (e.g., AWS S3 Operator) results in an `AccessDenied` error because no credentials can be supplied. ### Expected Behavior The Plugin configuration page should display the `identity` input fields defined in the `manifest.yaml` so that users can provide their AWS credentials. ### Actual Behavior The configuration UI is empty or missing the credential input fields entirely, leading to unauthorized API calls. ### Technical Evidence In the plugin's `manifest.yaml`, the following identity fields are defined but not shown in the UI: ```yaml identity: aws_access_key_id: type: text-input required: true aws_secret_access_key: type: secret-input required: true aws_region: type: text-input required: true ``` ### Environment * Dify Cloud (SaaS) * Plugin: AWS Tools (langgenius/aws_tools) v0.0.17 ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:21:05 -05:00
yindo commented 2026-02-16 10:21:06 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 3, 2026):

Hi @ytnobody, thanks for opening this issue.

Why this is being closed

Dify issue tracking requires English-only issue title and description for consistent collaboration.

Next steps

Please open a new issue in English and include clear details so maintainers can help efficiently.

Thanks for understanding and for your support.

@crazywoola commented on GitHub (Feb 3, 2026): Hi @ytnobody, thanks for opening this issue. ### Why this is being closed Dify issue tracking requires English-only issue title and description for consistent collaboration. ### Next steps Please open a new issue in English and include clear details so maintainers can help efficiently. Thanks for understanding and for your support.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#950
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?