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

Confluence plugin: add dropdown to ask for Basic vs PAT token #495

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

Originally created by @frenoid on GitHub (Jul 28, 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.7.0

Plugin version

confluence 0.0.2

Cloud or Self Hosted

Self Hosted (Source), Self Hosted (Docker)

Steps to reproduce

Not exactly a bug report but a feature request to handle Confluence tokens in a more user-friendly way.

Steps

  1. Generate Confluence PAT token:
  2. Authorize Confluence plugin in Dify
  3. Enter Authorization Name, Confluence URL, and Access Token as "{PATtoken}"
  4. Dify shows Authorization as success
  5. When I "Get the content of a Confluence page" in workflow, it fails with 401

How I Fixed

  1. Enter the Access Token as "Bearer {PATtoken}"

Enhancement request

Add a dropdown box named "Token type" to the confluence plugin with 2 options

  1. Basic
  2. PAT

Confluence plugin can handle the Authorization header accordingly

  1. Select Basic -> Authorization: Basic {token}
  2. Select Bearer -> Authorization: Bearer {token}

Related code:
https://github.com/langgenius/dify-official-plugins/pull/919/commits/620363b2b47a966532a0ce24eb0d04a5b0f952f0

✔️ Error log

No response

Originally created by @frenoid on GitHub (Jul 28, 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.7.0 ### Plugin version confluence 0.0.2 ### Cloud or Self Hosted Self Hosted (Source), Self Hosted (Docker) ### Steps to reproduce Not exactly a bug report but a feature request to handle Confluence tokens in a more user-friendly way. Steps === 1. Generate Confluence PAT token: <PATtoken> 2. Authorize Confluence plugin in Dify 3. Enter Authorization Name, Confluence URL, and Access Token as "{PATtoken}" 4. Dify shows Authorization as success 5. When I "Get the content of a Confluence page" in workflow, it fails with 401 How I Fixed === 1. Enter the Access Token as "Bearer {PATtoken}" Enhancement request === Add a dropdown box named "Token type" to the confluence plugin with 2 options 1. Basic 2. PAT Confluence plugin can handle the Authorization header accordingly 1. Select Basic -> Authorization: Basic {token} 2. Select Bearer -> Authorization: Bearer {token} Related code: https://github.com/langgenius/dify-official-plugins/pull/919/commits/620363b2b47a966532a0ce24eb0d04a5b0f952f0 ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:19:34 -05:00
yindo closed this issue 2026-02-16 10:19:34 -05:00
yindo commented 2026-02-16 10:19:34 -05:00
Author
Owner
Copy Link
Copy Source

@frenoid commented on GitHub (Jul 29, 2025):

changed <token> to {token} to avoid markdown making them invisible

@frenoid commented on GitHub (Jul 29, 2025): changed `<token>` to `{token}` to avoid markdown making them invisible
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#495
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?