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

[PR #31567] fix: clear all default providers in tenant for enterprise mode #33304

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

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

State: open
Merged: No

Summary

  • Fixes EE-1511: When setting a new default tool credential in enterprise mode, properly clears ALL existing defaults for that provider in the tenant

Problem

In enterprise mode, credentials synced from global have a different user_id than locally-created credentials. The existing code only cleared defaults for credentials with the same user_id, resulting in multiple credentials having is_default=true simultaneously.

This caused the credential usage check to incorrectly show workflows as "using" a credential that was no longer the effective default.

Solution

  • Enterprise mode: Clear all is_default=true for the provider in the tenant (regardless of user_id)
  • Non-enterprise mode: Preserve original behavior (only clear defaults for current user)

Related

  • Companion PR in enterprise repo handles detecting default credential usage in workflows
**Original Pull Request:** https://github.com/langgenius/dify/pull/31567 **State:** open **Merged:** No --- ## Summary - Fixes EE-1511: When setting a new default tool credential in enterprise mode, properly clears ALL existing defaults for that provider in the tenant ## Problem In enterprise mode, credentials synced from global have a different `user_id` than locally-created credentials. The existing code only cleared defaults for credentials with the same `user_id`, resulting in multiple credentials having `is_default=true` simultaneously. This caused the credential usage check to incorrectly show workflows as "using" a credential that was no longer the effective default. ## Solution - Enterprise mode: Clear all `is_default=true` for the provider in the tenant (regardless of `user_id`) - Non-enterprise mode: Preserve original behavior (only clear defaults for current user) ## Related - Companion PR in enterprise repo handles detecting default credential usage in workflows
yindo added the pull-request label 2026-02-21 20:53:02 -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#33304
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?