Describe the bug:
I have configured RBAC in Milvus by granting DatabaseReadWrite and CollectionReadWrite privileges to a role and attaching this role to a user. These privileges are granted on a non-default database.
When I log in to Attu using this user:
The non-default database is visible
All collections under the database are listed
However, the collections appear empty in Attu (no data shown)
If I access the same database and collections using an admin/superuser or via SDK, the collections are present and contain data.
This seems to be an issue with how Attu handles RBAC permissions for collections in non-default databases.
Steps to reproduce:
- Create a non-default database in Milvus
- Create collections and insert data into the non-default database
- Create a role and grant the following privileges on the non-default database:
DatabaseReadWrite
CollectionReadWrite
- Attach the role to a user
- Log in to Attu using this user
- Select the non-default database
- Open any collection
Attu version:
2.5.12
Milvus version:
2.5.13
Describe the bug:
I have configured RBAC in Milvus by granting DatabaseReadWrite and CollectionReadWrite privileges to a role and attaching this role to a user. These privileges are granted on a non-default database.
When I log in to Attu using this user:
The non-default database is visible
All collections under the database are listed
However, the collections appear empty in Attu (no data shown)
If I access the same database and collections using an admin/superuser or via SDK, the collections are present and contain data.
This seems to be an issue with how Attu handles RBAC permissions for collections in non-default databases.
Steps to reproduce:
DatabaseReadWrite
CollectionReadWrite
Attu version:
2.5.12
Milvus version:
2.5.13