[Bug]: does tool supports client certificates?

[nishantchauhan04]

Current Behavior

After enabling authorization, where do i keep my client certificate ?

milvus:
  address: localhost
  port: 19530
  authorizationEnabled: true

getting below error while checking

root@milvus-backup-tool:/opt/milvus# ./milvus-backup check --config "backup-dev.yaml"
0.4.17 (Built on 2024-07-04T09:53:00Z from Git SHA 197ad69b6bc5f4b3f47c7150386b47fe8f2180ee)
config:backup-dev.yaml
[2024/07/24 11:30:03.690 +00:00] [INFO] [logutil/logutil.go:165] ["Log directory"] [configDir=]
[2024/07/24 11:30:03.690 +00:00] [INFO] [logutil/logutil.go:166] ["Set log file to "] [path=logs/backup-dev.log]
[2024/07/24 11:30:03.692 +00:00] [DEBUG] [core/backup_context.go:62] ["Start Milvus client"] [endpoint=10.240.64.10:19530]
[2024/07/24 11:30:03.708 +00:00] [WARN] [grpclog/grpclog.go:46] ["[core][Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {\n  \"Addr\": \"10.240.64.10:19530\",\n  \"ServerName\": \"10.240.64.10:19530\",\n  \"Attributes\": null,\n  \"BalancerAttributes\": null,\n  \"Type\": 0,\n  \"Metadata\": null\n}. Err: connection error: desc = \"transport: authentication handshake failed: x509: cannot validate certificate for 10.240.64.10 because it doesn't contain any IP SANs\""]

Expected Behavior

Succeed to connect to milvus and storage.
Milvus version: v2.3
Storage:
milvus-bucket: a-bucket
milvus-rootpath: files
backup-bucket: a-bucket
backup-rootpath: backup

Steps To Reproduce

1. enable   authorizationEnabled: true

Environment

No response

Anything else?

No response