[Bug]: When deploying Milvus, authentication was enabled, but the web UI can still be accessed without a username/password.

[zhuwenxing]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:master/2.5
- Deployment mode(standalone or cluster):with auth enabled
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

When deploying Milvus, authentication was enabled, but the web UI can still be accessed without a username/password.

Expected Behavior

The web UI should have authentication capabilities like Attu

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @jaime0815
/unassign

[jaime0815]

WebUI is intended solely for DevOps or developers, so we do not plan to support username and password functionality.

[zhuwenxing]

Completely removing username and password functionality may introduce security and compliance risks. Even if the target users are developers or DevOps, basic security measures should not be overlooked.

[xiaofan-luan]

agreed we need a login user/password support, we only need to verify the username/password once when the webUI is up

@jaime0815 please help on it