Milvus authentication boundary

Evidence-backed facts

1. Milvus documents user authentication as an explicitly enabled server control and treats TLS and user authentication as distinct security approaches. informative
2. After authentication is enabled, a client connects with configured user credentials and an invalid token produces an authentication error. informative
3. Creating, updating, listing, or dropping users are separate authenticated administration operations rather than consequences of ordinary connectivity. informative
4. The documentation shows a default root credential for initial access and separate password and super-user controls; a documentation record does not create a secured deployment or authorize any data operation. informative

Primary sources