langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

The UI of the Confluence plugin in Dify doesn't match the documentation. #632

New Issue
Closed
opened 2026-02-16 10:19:59 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:19:59 -05:00
Owner
Copy Link
Copy Source

Originally created by @Ryniasaki on GitHub (Sep 9, 2025).

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

1.8.1

Plugin version

0.0.3

Cloud or Self Hosted

Cloud

Steps to reproduce

Click the "API Key Authorization" button.
Image
The actual configuration interface differs from the one in the documentation; it's missing the "Username" field.
Image
Image
This caused the configuration to fail.

✔️ Error log

No response

Originally created by @Ryniasaki on GitHub (Sep 9, 2025). ### 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 1.8.1 ### Plugin version 0.0.3 ### Cloud or Self Hosted Cloud ### Steps to reproduce Click the "API Key Authorization" button. <img width="506" height="158" alt="Image" src="https://github.com/user-attachments/assets/14a624e6-9459-400c-be95-bd1034572904" /> The actual configuration interface differs from the one in the documentation; it's missing the "Username" field. <img width="760" height="501" alt="Image" src="https://github.com/user-attachments/assets/d52b8694-e44e-48c1-b3df-fd57863053c2" /> <img width="914" height="519" alt="Image" src="https://github.com/user-attachments/assets/8b2ad81a-c792-4db0-b94a-84bf8b8a9807" /> This caused the configuration to fail. ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:19:59 -05:00
yindo closed this issue 2026-02-16 10:19:59 -05:00
yindo commented 2026-02-16 10:19:59 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 9, 2025):

Hi @Ryniasaki! I'm Dosu and I’m helping the dify-official-plugins team.

The current Confluence plugin UI in Dify (v0.0.3) is designed to use email and API token for authentication, and does not include a separate 'Username' field. This change aligns with Atlassian's recommended authentication method and recent updates to the plugin, which now favor email+APIToken over username-based authentication. The documentation may not have been updated to reflect this change, which is why you're seeing a discrepancy between the UI and the docs. For successful configuration, use your email and API token in the provided fields; username-based authentication is no longer supported in the current UI design. More details on this change can be found in related discussions here and here.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 9, 2025): <!-- Greeting --> Hi @Ryniasaki! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> The current Confluence plugin UI in Dify (v0.0.3) is designed to use email and API token for authentication, and does not include a separate 'Username' field. This change aligns with Atlassian's recommended authentication method and recent updates to the plugin, which now favor email+APIToken over username-based authentication. The documentation may not have been updated to reflect this change, which is why you're seeing a discrepancy between the UI and the docs. For successful configuration, use your email and API token in the provided fields; username-based authentication is no longer supported in the current UI design. More details on this change can be found in related discussions [here](https://github.com/langgenius/dify-official-plugins/issues/1372) and [here](https://github.com/langgenius/dify-official-plugins/issues/911). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/5454f0eb-7ea0-410e-b79f-f971632e7df4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5454f0eb-7ea0-410e-b79f-f971632e7df4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5454f0eb-7ea0-410e-b79f-f971632e7df4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5454f0eb-7ea0-410e-b79f-f971632e7df4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5454f0eb-7ea0-410e-b79f-f971632e7df4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5454f0eb-7ea0-410e-b79f-f971632e7df4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5454f0eb-7ea0-410e-b79f-f971632e7df4?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1680)
yindo commented 2026-02-16 10:19:59 -05:00
Author
Owner
Copy Link
Copy Source

@MevionCN commented on GitHub (Sep 10, 2025):

@dosu
below is the current API Key Authorization Configuration page, there're [Authorization Name],[Confluence URL] and [Access Token] filed, no email filed. how we can complete the API Configuration?

Image

my appreciate for your support.

@MevionCN commented on GitHub (Sep 10, 2025): @dosu below is the current API Key Authorization Configuration page, there're [Authorization Name],[Confluence URL] and [Access Token] filed, no email filed. how we can complete the API Configuration? <img width="798" height="557" alt="Image" src="https://github.com/user-attachments/assets/5ce7e2a2-51a2-46f8-ada0-5f439da0a3e5" /> my appreciate for your support.
yindo commented 2026-02-16 10:19:59 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 26, 2025):

Hi, @Ryniasaki. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that the Confluence plugin UI in Dify v1.8.1 (plugin v0.0.3) on cloud lacks the "Username" field in API Key Authorization.
  • The plugin now uses email and API token for authentication, following Atlassian's updated recommendations.
  • The documentation was outdated and did not reflect these UI changes.
  • Another user also noted confusion about how to complete configuration without an email field visible.
  • The maintainers acknowledged the need to update the documentation to clarify the authentication process.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If no further updates are provided, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 26, 2025): Hi, @Ryniasaki. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that the Confluence plugin UI in Dify v1.8.1 (plugin v0.0.3) on cloud lacks the "Username" field in API Key Authorization. - The plugin now uses email and API token for authentication, following Atlassian's updated recommendations. - The documentation was outdated and did not reflect these UI changes. - Another user also noted confusion about how to complete configuration without an email field visible. - The maintainers acknowledged the need to update the documentation to clarify the authentication process. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If no further updates are provided, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!
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#632
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?