userdbctlsystemduserdbctl1userdbctlInspect users, groups and group membershipsuserdbctlOPTIONSCOMMANDNAMEDescriptionuserdbctl may be used to inspect user and groups (as well as group memberships)
of the system. This client utility inquires user/group information provided by various system services,
both operating on JSON user/group records (as defined by the JSON User Records and JSON Group Records definitions), and classic UNIX NSS/glibc
user and group records. This tool is primarily a client to the User/Group Record Lookup API via Varlink, and may also
pick up drop-in JSON user and group records from /etc/userdb/,
/run/userdb/, /run/host/userdb/,
/usr/lib/userdb/.OptionsThe following options are understood:MODEChoose the output mode, takes one of classic,
friendly, table, json. If
classic, an output very close to the format of /etc/passwd or
/etc/group is generated. If friendly a more comprehensive and
user friendly, human readable output is generated; if table a minimal, tabular
output is generated; if json a JSON formatted output is generated. Defaults to
friendly if a user/group is specified on the command line,
table otherwise.Note that most output formats do not show all available information. In particular,
classic and table show only the most important fields. Various
modes also do not show password hashes. Use json to view all fields, including
any authentication fields.SERVICE:SERVICE…SERVICE:SERVICE…Controls which services to query for users/groups. Takes a list of one or more
service names, separated by :. See below for a list of well-known service
names. If not specified all available services are queried at once.BOOLControls whether to include classic glibc/NSS user/group lookups in the output. If
is used any attempts to resolve or enumerate users/groups provided
only via glibc NSS is suppressed. If is specified such users/groups
are included in the output (which is the default).BOOLControls whether to include Varlink user/group lookups in the output, i.e. those done
via the User/Group Record Lookup API via
Varlink. If is used any attempts to resolve or enumerate
users/groups provided only via Varlink are suppressed. If is
specified such users/groups are included in the output (which is the default).BOOLControls whether to include user/group lookups in the output that are defined using
drop-in files in /etc/userdb/, /run/userdb/,
/run/host/userdb/, /usr/lib/userdb/. If
is used these records are suppressed. If
is specified such users/groups are included in the output (which
is the default).BOOLControls whether to synthesize records for the root and nobody users/groups if they
aren't defined otherwise. By default (or yes) such records are implicitly
synthesized if otherwise missing since they have special significance to the OS. When
no this synthesizing is turned off.This option is short for
. Use this option to show only records that are natively defined as
JSON user or group records, with all NSS/glibc compatibility and all implicit synthesis turned
off.CommandsThe following commands are understood:userUSER…List all known users records or show details of one or more specified user
records. Use to tweak output mode.groupGROUP…List all known group records or show details of one or more specified group
records. Use to tweak output mode.users-in-groupGROUP…List users that are members of the specified groups. If no groups are specified list
all user/group memberships defined. Use to tweak output
mode.groups-of-userUSER…List groups that the specified users are members of. If no users are specified list
all user/group memberships defined (in this case groups-of-user and
users-in-group are equivalent). Use to tweak output
mode.servicesList all services currently providing user/group definitions to the system. See below
for a list of well-known services providing user information.ssh-authorized-keysThis operation is not a public, user-facing interface. It is used to allow the SSH daemon to pick
up authorized keys from user records, see below.Well-Known ServicesThe userdbctl services command will list all currently running services that
provide user or group definitions to the system. The following well-known services are shown among
this list:io.systemd.DynamicUserThis service is provided by the system service manager itself (i.e. PID 1) and
makes all users (and their groups) synthesized through the DynamicUser= setting in
service unit files available to the system (see
systemd.exec5 for
details about this setting).io.systemd.HomeThis service is provided by
systemd-homed.service8
and makes all users (and their groups) belonging to home directories managed by that service
available to the system.io.systemd.MachineThis service is provided by
systemd-machined.service8
and synthesizes records for all users/groups used by a container that employs user
namespacing.io.systemd.MultiplexerThis service is provided by
systemd-userdbd.service8
and multiplexes user/group look-ups to all other running lookup services. This is the primary entry point
for user/group record clients, as it simplifies client side implementation substantially since they
can ask a single service for lookups instead of asking all running services in parallel.
userdbctl uses this service preferably, too, unless
or are used, in which case finer control over the services to talk to is
required.io.systemd.NameServiceSwitchThis service is (also) provided by
systemd-userdbd.service8
and converts classic NSS/glibc user and group records to JSON user/group records, providing full
backwards compatibility. Use to disable this compatibility, see
above. Note that compatibility is actually provided in both directions:
nss-systemd8 will
automatically synthesize classic NSS/glibc user/group records from all JSON user/group records
provided to the system, thus using both APIs is mostly equivalent and provides access to the same
data, however the NSS/glibc APIs necessarily expose a more reduced set of fields
only.io.systemd.DropInThis service is (also) provided by
systemd-userdbd.service8
and picks up JSON user/group records from /etc/userdb/,
/run/userdb/, /run/host/userdb/,
/usr/lib/userdb/.Note that userdbctl has internal support for NSS-based lookups too. This means
that if neither io.systemd.Multiplexer nor
io.systemd.NameServiceSwitch are running look-ups into the basic user/group
databases will still work.Integration with SSHThe userdbctl tool may be used to make the list of SSH authorized keys possibly
contained in a user record available to the SSH daemon for authentication. For that configure the
following in sshd_config5:…
AuthorizedKeysCommand /usr/bin/userdbctl ssh-authorized-keys %u
AuthorizedKeysCommandUser root
…Exit statusOn success, 0 is returned, a non-zero failure code otherwise.See Alsosystemd1,
systemd-userdbd.service8,
systemd-homed.service8,
nss-systemd8,
getent1