rpk acl user
Manage SCRAM users.
If SCRAM is enabled, a SCRAM user is what you use to talk to Redpanda, and ACLs
control what your user has access to. See rpk acl --help for more information
about ACLs, and rpk acl user create --help for more information about
creating SCRAM users. Using SCRAM requires setting kafka_enable_authorization: true and authentication_method: sasl in the
redpanda section of your redpanda.yaml, and setting sasl_mechanisms with SCRAM for your Redpanda cluster.
Flags
| Value | Type | Description |
|---|---|---|
|
strings |
The comma-separated list of Admin API addresses (<ip>:<port>). You must specify one for each node. |
|
- |
Help for user. |
|
string |
The certificate to be used for TLS authentication with the Admin API. |
|
- |
Enable TLS for the Admin API (not necessary if specifying custom certs). |
|
string |
The certificate key to be used for TLS authentication with the Admin API. |
|
string |
The truststore to be used for TLS communication with the Admin API. |
|
strings |
Comma-separated list of broker ip:port pairs (e.g. --brokers '192.168.78.34:9092,192.168.78.35:9092,192.179.23.54:9092'). Alternatively, you may set the REDPANDA_BROKERS environment variable with the comma-separated list of broker addresses. |
|
string |
Redpanda config file, if not set the file will be searched for in the default locations. |
|
string |
SASL password to be used for authentication. |
|
string |
The authentication mechanism to use. Supported values: SCRAM-SHA-256, SCRAM-SHA-512. |
|
string |
The certificate to be used for TLS authentication with the broker. |
|
- |
Enable TLS for the Kafka API (not necessary if specifying custom certs). |
|
string |
The certificate key to be used for TLS authentication with the broker. |
|
string |
The truststore to be used for TLS communication with the broker. |
|
string |
SASL user to be used for authentication. |
|
- |
Enable verbose logging (default: false). |