langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 11:11:21 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #26615] fix bug 26613: get wrong credentials with multiple authorizations plugin #31493

New Issue
Closed
opened 2026-02-21 20:49:34 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:49:34 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/26615

State: closed
Merged: Yes

Summary

The plugins configured multiple authorizations can only retrieve the first configuration from API. The root cause is reusing encrypters per credential_type causes decrypted credentials to be identical across provider entries because the encrypter's cache is keyed by provider identity, not credential_type.

fix #26613

Screenshots

Before After
image image

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/26615 **State:** closed **Merged:** Yes --- ## Summary The plugins configured multiple authorizations can only retrieve the first configuration from API. The root cause is reusing encrypters per credential_type causes decrypted credentials to be identical across provider entries because the encrypter's cache is keyed by provider identity, not credential_type. fix #26613 ## Screenshots | Before | After | |--------|-------| | <img width="1076" height="615" alt="image" src="https://github.com/user-attachments/assets/62c90ad8-702d-4e43-9fdb-a8ef3f0d0fb9" /> | <img width="1141" height="592" alt="image" src="https://github.com/user-attachments/assets/d1d2954d-a975-4e8b-83c2-279c3bfd58fc" /> | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:49:34 -05:00
yindo closed this issue 2026-02-21 20:49:34 -05:00
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 pull-request
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#31493
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?