ACL GETUSER

Lists the ACL rules of a user.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	ACL GETUSER
Catalog group	Server commands
Upstream since	6.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

ACL GETUSER username

ffkv behavior and limits

Server introspection describes ffkv, not a Redis process. MEMORY reports owned-allocation estimates, not jemalloc accounting. Administrative changes can affect all clients or persistent data; consult the scenario and operations guide before using destructive forms.

Source: README.md:393–395, 601–642; tests/bdd/features/server.feature; tests/bdd/features/catalog.feature.

All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.

Upstream metadata

The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.

Upstream Redis complexity: O(N). Where N is the number of password, command and pattern rules that the user has.

Upstream arity: 3 (includes the command name; a negative number is a minimum).

Command flags: ADMIN, NOSCRIPT, LOADING, STALE, SENTINEL.

Argument structure

Argument	Type	Constraints / metadata
username	string	Required

Additional pinned upstream metadata

{
  "group": "server",
  "since": "6.0.0",
  "history": [
    [
      "6.2.0",
      "Added Pub/Sub channel patterns."
    ],
    [
      "7.0.0",
      "Added selectors and changed the format of key and channel patterns from a list to their rule representation."
    ]
  ]
}

Metadata source · Local snapshot: src/command_metadata.json, key acl|getuser.

BDD coverage and source examples

These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.

• Hashed passwords are genuine credentials and can be removed by hash — tests/bdd/features/server.feature:1107; command tag.
• Selectors expose their real rules and cannot combine permissions across selectors — tests/bdd/features/server.feature:1136; command tag and invocation observed.
• User enumeration and removal reflect live state without deleting default — tests/bdd/features/server.feature:1267; command tag and invocation observed.
• Saved ACL rules reload atomically and survive a server restart — tests/bdd/features/server.feature:1385; invocation observed.

Extracted command vectors

The following JSON arrays are the test harness’s argument vectors, not shell commands. Numeric arguments are converted by the harness; objects of the form {"base64":"…"} represent decoded binary bytes, not a literal JSON command argument. Preserve scenario setup and connection ordering. See the CLI guide for shell quoting and binary stdin. No reply is invented or inferred.

Selectors expose their real rules and cannot combine permissions across selectors — tests/bdd/features/server.feature:1143 (client “admin” executes:)

[
  "ACL",
  "GETUSER",
  "selected"
]

Next source assertion: the reply contains:

{"commands":"-@all +get","keys":"~read:*","channels":"","selectors":[{"commands":"-@all +set","keys":"~write:*","channels":""}]}

User enumeration and removal reflect live state without deleting default — tests/bdd/features/server.feature:1297 (I execute:)

[
  "ACL",
  "GETUSER",
  "enumerated"
]

Next source assertion: the reply is null

Saved ACL rules reload atomically and survive a server restart — tests/bdd/features/server.feature:1423 (I execute:)

[
  "ACL",
  "GETUSER",
  "unsaved-user"
]

Next source assertion: the reply is null