[ZOOKEEPER-3476] Identify client request for quota control

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: server
• Assignee: Unassigned
• Reporter: Mocheng Guo
• Created: 29/Jul/19 23:17
• Updated: 06/Aug/19 00:25

Description

In order to support quota, we need a way to identify clients. If security is enabled, we might be able to use secured identity inside client certificate. But a generalized client-id based approach would be better to cover scenario without security.

The proposal here is to utilize existing zookeeper auth protocol to accept client identity.

1. The client id should be sent by client once connection is established.
2. Sending client id is optional. Note that server needs to enable auth provider if client does send in client id auth request or request would be denied without auth provider on server side.
3. client id is JSON withe client_id as mandatory field. Additional fields can be added like client contact information, client version...
4. This client identity will be cached in server connection and attached to requests from the connection.