Hi team, I am trying out ZkBasicAuthAccessControl ...
# troubleshooting
d
Hi team, I am trying out ZkBasicAuthAccessControl in our dev environment. So far it has been working well, I am able to log in with the inital user, and also able to create more users. However, I notice if I create a USER with READ permission on a table, this user will NOT be able to log into the Controller UI, but this USER is able to query the table via /sql endpoint. I will post the reproduction steps in the thread.
I am using Pinot version 1.3.0 and this is how we enable ZK auth:
Copy code
controller-config:
    controller.admin.access.control.factory.class=org.apache.pinot.controller.api.access.ZkBasicAuthAccessControlFactory

access.control.init.username=admin
access.control.init.password=password
Copy code
broker-config:
        pinot.broker.access.control.class=org.apache.pinot.broker.broker.ZkBasicAuthAccessControlFactory
this is how I create this test-user: curl --request POST --url http://controller-url/users -d '{ "username": "test-user", "password": "test-user", "component": "controller", "role": "user", "tables": ["test_table"], "permissions": ["READ"] }' curl --request POST --url http://controller-url/users -d '{ "username": "test-user", "password": "test-user", "component": "broker", "role": "user", "tables": ["test_table"], "permissions": ["READ"] }' And then logging in with the same user credentials will receive Invalid Username/Password error.
I think login failure is because the /auth/verify endpoint doesn't include a tableName in its path, which leads the hasTable(String tableName) method always returns false. Is this an expected behaviour?
x
Right, I think we could extend the backend API to make this work, do you want to take this up and create a PR? I can help review and merge it
d
Sure. I will tag you once we get to this. 🙂