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

Confluence plugin: token_type dropdown field missing (Issue #1372 not fully resolved) #689

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

Originally created by @HaRuKa-1231 on GitHub (Oct 6, 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.9.1

Plugin version

0.0.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Environment

  • Confluence: Cloud (e.g., https://your-domain.atlassian.net)
  • Authentication method required: Basic authentication with API token

Current Behavior

  1. Install Confluence plugin (v0.0.3) from marketplace
  2. Try to configure credentials with:
    • URL: https://your-domain.atlassian.net
    • Token: base64 encoded email:api_token
  3. Authentication fails with 401 Unauthorized

Root Cause

The token_type field is missing in provider/confluence.yaml. Even though PR #1392 fixed the authentication header issue in auth.py (by reading token_type with default value 'Bearer'), users
cannot select the token type because there's no UI field for it.

Current implementation:

  • auth.py line 10: token_type = credential.get('token_type', 'Bearer')
  • confluence.yaml: No token_type field exists
  • Result: Always uses Bearer authentication (suitable for on-premise only)

Expected Behavior

Users should be able to select the authentication type:

  • Basic: For Confluence Cloud (with base64 encoded email:api_token)
  • Bearer: For Confluence Server/Data Center (with Personal Access Token)

Reference

✔️ Error log

req_id: 63fbb6f96c PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"Confluence authentication failed: Current user not permitted to use Confluence"}
Originally created by @HaRuKa-1231 on GitHub (Oct 6, 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.9.1 ### Plugin version 0.0.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ### Environment - Confluence: **Cloud** (e.g., `https://your-domain.atlassian.net`) - Authentication method required: **Basic authentication** with API token ### Current Behavior 1. Install Confluence plugin (v0.0.3) from marketplace 2. Try to configure credentials with: - URL: `https://your-domain.atlassian.net` - Token: base64 encoded `email:api_token` 3. Authentication fails with 401 Unauthorized ### Root Cause The `token_type` field is missing in `provider/confluence.yaml`. Even though PR #1392 fixed the authentication header issue in `auth.py` (by reading `token_type` with default value 'Bearer'), **users cannot select the token type** because there's no UI field for it. Current implementation: - `auth.py` line 10: `token_type = credential.get('token_type', 'Bearer')` - `confluence.yaml`: **No `token_type` field exists** - Result: Always uses Bearer authentication (suitable for on-premise only) ### Expected Behavior Users should be able to select the authentication type: - **Basic**: For Confluence Cloud (with base64 encoded `email:api_token`) - **Bearer**: For Confluence Server/Data Center (with Personal Access Token) ### Reference - Confluence Cloud uses Basic auth: https://developer.atlassian.com/cloud/confluence/basic-auth-for-rest-apis/ - Confluence Server/DC uses Bearer auth: https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html - Related issues: #911, #1372 - Related PR: #919, #1392 (partially fixed, but missing UI field) ### ✔️ Error log ``` req_id: 63fbb6f96c PluginInvokeError: {"args":{},"error_type":"ToolProviderCredentialValidationError","message":"Confluence authentication failed: Current user not permitted to use Confluence"} ```
yindo added the bug label 2026-02-16 10:20:12 -05:00
yindo closed this issue 2026-02-16 10:20:12 -05:00
yindo commented 2026-02-16 10:20:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 6, 2025):

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

The Confluence plugin still does not support selecting the authentication type (Basic or Bearer) via the UI or YAML config. The token_type dropdown and corresponding YAML field are missing, so the plugin always defaults to Bearer authentication, which causes 401 errors for Confluence Cloud users who require Basic auth with a base64 encoded email:api_token. This issue is documented and remains unresolved as of the latest code and plugin version source.

There are no recent pull requests or updates that add this feature. For now, there is no official workaround to manually set token_type; users cannot select the authentication method in the current plugin. You can follow progress and future updates in the relevant issues #1372 and #911.

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 (Oct 6, 2025): <!-- Greeting --> Hi @HaRuKa-1231! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> The Confluence plugin still does not support selecting the authentication type (Basic or Bearer) via the UI or YAML config. The token_type dropdown and corresponding YAML field are missing, so the plugin always defaults to Bearer authentication, which causes 401 errors for Confluence Cloud users who require Basic auth with a base64 encoded email:api_token. This issue is documented and remains unresolved as of the latest code and plugin version [source](https://github.com/langgenius/dify-official-plugins/issues/1372). There are no recent pull requests or updates that add this feature. For now, there is no official workaround to manually set token_type; users cannot select the authentication method in the current plugin. You can follow progress and future updates in the relevant issues [#1372](https://github.com/langgenius/dify-official-plugins/issues/1372) and [#911](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/f5998480-657c-4660-b056-dd4a9c709962?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f5998480-657c-4660-b056-dd4a9c709962?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f5998480-657c-4660-b056-dd4a9c709962?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f5998480-657c-4660-b056-dd4a9c709962?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f5998480-657c-4660-b056-dd4a9c709962?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f5998480-657c-4660-b056-dd4a9c709962?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f5998480-657c-4660-b056-dd4a9c709962?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/1807)
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#689
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?