[Bug]: RBAC permission denied after restart with star privilege

[shaoting-huang]

Is there an existing issue for this?

• I have searched the existing issues

Environment

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

Current Behavior

Existing permissions get denied after restarting with Milvus if there is a privilege name "*" granted. See details: #40015

Expected Behavior

Should restore all existing permissions after restarting Milvus

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

[dosubot]

Hey @shaoting-huang! 👋 I'm here to help you out with any bugs, questions, or contributions you have in mind. Let's squash those bugs together!

The issue you're experiencing with RBAC permissions being denied after a restart, particularly when using the privilege name "", might be related to how Milvus manages and persists these permissions. The privilege name "" is intended to grant global permissions across all collections or resources, simplifying permission management ^[1][2]. However, it seems there might be a problem with how these permissions are being restored after a restart.

Unfortunately, I couldn't find specific information on how Milvus persists RBAC permissions across restarts or any known issues related to this in the documentation or codebase. It might be beneficial to check if there are any updates or patches available for your current version (2.5.4) that address this issue. Additionally, reviewing the discussion linked in your message might provide further insights or workarounds shared by other users facing similar issues.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yanliang567]

working on the verification