How Does the Milvus Vector Database Ensure Data Security?
Sep 5, 2022Angela Ni

Summary
This post details the implementation of user authentication and TLS connection in Milvus 2.1. User authentication is handled by the Milvus proxy, which intercepts gRPC requests and verifies credentials stored in etcd using bcrypt. The workflow for authentication and credential updates is described, along with configuration steps in `milvus.yaml` and SDK examples for connecting with credentials. TLS is enabled by configuring server and CA certificates in `milvus.yaml` and providing client certificates for SDK connections.
More from the Role-Based Access Control (RBAC) trail
- Milvus Access Control Guide: How to Configure RBAC for Production
- Milvus RBAC Explained: Secure Your Vector Database with Role-Based Access Control
- Designing Multi-Tenancy RAG with Milvus: Best Practices for Scalable Enterprise Knowledge Bases
- Milvus 2.2.10 & 2.2.11: Minor Updates for Enhanced System Stability and User Experience