You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ctubbsii (via GitHub)" <gi...@apache.org> on 2023/05/26 17:29:32 UTC
[GitHub] [accumulo] ctubbsii opened a new issue, #3434: Some AccumuloClient API operations do not require an authenticated user
ctubbsii opened a new issue, #3434:
URL: https://github.com/apache/accumulo/issues/3434
Issue #3427 highlighted the fact that some API operations do not require the client to have been constructed using an authenticated users. In the case of a bug, this could happen because the RPC endpoint doesn't authenticate the user correctly. Those cases should absolutely be fixed. However, there are also cases where this occurs because the operation is a ZooKeeper-only operation, and does not require communicating with an Accumulo service. The example in #3427 was the ability to list tables, but there may be others (list namespaces, etc.)
Even if authentication is added to the Accumulo code to perform these operations, the information is still visible in ZooKeeper using zkCli.sh or another ZK client, because they are world-readable.
This issue is to propose:
1. identifying those operations where authentication isn't needed,
2. consider the impact of locking down the information in ZK so they are not world-readable, and
3. adding an authenticated RPC endpoint in Accumulo services to perform the operation for the client, and changing the client implementation to use that RPC endpoint instead of talking directly to ZK.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org