How Does the Milvus Vector Database Ensure Data Security?

What this post added

This post details the implementation of user authentication and TLS connection in Milvus 2.1. User authentication involves a workflow where the Milvus proxy verifies credentials (username and password) against stored information in etcd, using bcrypt for password encryption. Credentials are cached locally in the proxy for performance. The post outlines how to enable authentication in `milvus.yaml`, the default root user credentials, and how to create and reset user credentials using the SDK. TLS connection is enabled by configuring server and client certificates (`server.pem`, `server.key`, `ca.pem`) in `milvus.yaml` and providing client-side certificate paths during connection.