github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 07:43:10 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

feat: Milvus Vector Store Encryption Support #6465

New Issue
Closed
opened 2025-11-11 16:55:58 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 16:55:58 -06:00
Owner
Copy Link

Originally created by @flefevre on GitHub (Sep 22, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Is your feature request related to a problem? Please describe.
Currently, vector data stored in Milvus is not encrypted at rest. For organizations operating in regulated or security-sensitive environments, this creates compliance and data protection challenges.

Desired Solution you'd like

Introduce an experimental encryption option for Milvus, similar to the recently added 🔒 Table-Level PGVector Data Encryption feature.

  • Activate support for encrypting Milvus collections at the storage level.
  • Ensure vector embeddings and metadata remain secured at rest and during persistence.
  • Provide an optional configuration flag in open-webui to enable/disable encryption for Milvus, making it simple to adopt without complex external setup.

Alternatives Considered

  • Relying on infrastructure-level encryption (disk-level or cloud-managed). While useful, this does not provide fine-grained, database-level security for vectors.
  • Using external wrappers around Milvus, which adds complexity and isn’t integrated with Open WebUI.

Additional Context

This feature would mirror the security enhancement done for pgvector:

"🔒 Experimental Table-Level PGVector Data Encryption: Activate pgcrypto encryption support for pgvector to secure your vector search table contents, giving organizations enhanced compliance and data protection—perfect for enterprise or regulated environments."

By extending similar functionality to Milvus, Open WebUI would provide consistent enterprise-grade security across supported vector backends.

Potential benefits

  • Enhanced compliance (GDPR, HIPAA, etc.)
  • Stronger enterprise adoption
  • More secure handling of sensitive embeddings
Originally created by @flefevre on GitHub (Sep 22, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description **Is your feature request related to a problem? Please describe.** Currently, vector data stored in Milvus is not encrypted at rest. For organizations operating in regulated or security-sensitive environments, this creates compliance and data protection challenges. ### Desired Solution you'd like Introduce an **experimental encryption option for Milvus**, similar to the recently added **🔒 Table-Level PGVector Data Encryption** feature. - Activate support for encrypting Milvus collections at the storage level. - Ensure vector embeddings and metadata remain secured at rest and during persistence. - Provide an optional configuration flag in `open-webui` to enable/disable encryption for Milvus, making it simple to adopt without complex external setup. ### Alternatives Considered - Relying on infrastructure-level encryption (disk-level or cloud-managed). While useful, this does not provide fine-grained, database-level security for vectors. - Using external wrappers around Milvus, which adds complexity and isn’t integrated with Open WebUI. ### Additional Context This feature would mirror the security enhancement done for pgvector: > _"🔒 Experimental Table-Level PGVector Data Encryption: Activate pgcrypto encryption support for pgvector to secure your vector search table contents, giving organizations enhanced compliance and data protection—perfect for enterprise or regulated environments."_ By extending similar functionality to **Milvus**, Open WebUI would provide consistent enterprise-grade security across supported vector backends. **Potential benefits** - Enhanced compliance (GDPR, HIPAA, etc.) - Stronger enterprise adoption - More secure handling of sensitive embeddings
GiteaMirror commented 2025-11-11 16:55:59 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Sep 25, 2025):

We may have to wait for Offical Milvus support: https://github.com/milvus-io/milvus/issues/40013

@tjbck commented on GitHub (Sep 25, 2025): We may have to wait for Offical Milvus support: https://github.com/milvus-io/milvus/issues/40013
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#6465
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?