man/userdbctl.xml - main - niceSOFT/systemd

man/userdbctl.xml
523 строки25 KB
Yu Watanabe
man: mention userdb.transient.* credentials in userdbctl(1)
05 авг 2026, 05:38
05 авг 2026, 05:383273e22
<?xml version='1.0'?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->

<refentry id="userdbctl" conditional='ENABLE_USERDB'
    xmlns:xi="http://www.w3.org/2001/XInclude">

  <refentryinfo>
    <title>userdbctl</title>
    <productname>systemd</productname>
  </refentryinfo>

  <refmeta>
    <refentrytitle>userdbctl</refentrytitle>
    <manvolnum>1</manvolnum>
  </refmeta>

  <refnamediv>
    <refname>userdbctl</refname>
    <refpurpose>Inspect users, groups and group memberships</refpurpose>
  </refnamediv>

  <refsynopsisdiv>
    <cmdsynopsis>
      <command>userdbctl</command>
      <arg choice="opt" rep="repeat">OPTIONS</arg>
      <arg choice="req">COMMAND</arg>
      <arg choice="opt" rep="repeat">NAME</arg>
    </cmdsynopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>Description</title>

    <para><command>userdbctl</command> 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 <ulink
    url="https://systemd.io/USER_RECORD">JSON User Records</ulink> and <ulink
    url="https://systemd.io/GROUP_RECORD">JSON Group Records</ulink> definitions), and classic UNIX NSS/glibc
    user and group records. This tool is primarily a client to the <ulink
    url="https://systemd.io/USER_GROUP_API">User/Group Record Lookup API via Varlink</ulink>, and may also
    pick up drop-in JSON user and group records from <filename>/etc/userdb/</filename>,
    <filename>/run/userdb/</filename>, <filename>/run/host/userdb/</filename>,
    <filename>/usr/lib/userdb/</filename> (see
    <citerefentry><refentrytitle>nss-systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry> for
    details about drop-in user records).</para>
  </refsect1>

  <refsect1>
    <title>Options</title>

    <para>The following options are understood:</para>

    <variablelist>

      <varlistentry>
        <term><option>--output=<replaceable>MODE</replaceable></option></term>

        <listitem><para>Chooses the output mode. Takes one of <literal>classic</literal>,
        <literal>friendly</literal>, <literal>table</literal> or <literal>json</literal>. If
        <literal>classic</literal>, an output very close to the format of <filename>/etc/passwd</filename> or
        <filename>/etc/group</filename> is generated. If <literal>friendly</literal>, a more comprehensive and
        user friendly, human-readable output is generated. If <literal>table</literal>, a minimal, tabular
        output is generated. If <literal>json</literal>, a JSON formatted output is generated. Defaults to
        <literal>friendly</literal> if a user/group is specified on the command line,
        <literal>table</literal> otherwise.</para>

        <para>Note that most output formats do not show all available information. In particular,
        <literal>classic</literal> and <literal>table</literal> show only the most important fields. Various
        modes also do not show password hashes. Use <literal>json</literal> to view all fields, including
        any authentication fields.</para>

        <xi:include href="version-info.xml" xpointer="v245"/>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--json=<replaceable>FORMAT</replaceable></option></term>

        <listitem><para>Selects JSON output mode (like <option>--output=json</option>) and selects the
        precise display mode. Takes one of <literal>pretty</literal> or <literal>short</literal>. If
        <literal>pretty</literal>, human-friendly whitespace and newlines are inserted in the output to make
        the JSON data more readable. If <literal>short</literal>, all superfluous whitespace is
        suppressed.</para>

        <xi:include href="version-info.xml" xpointer="v250"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--service=<replaceable>SERVICE</replaceable><optional>:<replaceable>SERVICE…</replaceable></optional></option></term>
        <term><option>-s</option> <replaceable>SERVICE</replaceable>:<replaceable>SERVICE…</replaceable></term>

        <listitem><para>Controls which services to query for users/groups. Takes a list of one or more
        service names, separated by <literal>:</literal>. See below for a list of well-known service
        names. If not specified, all available services are queried at once.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--with-nss=<replaceable>BOOL</replaceable></option></term>

        <listitem><para>Controls whether to include classic glibc/NSS user/group lookups in the output. If
        <option>--with-nss=no</option> is used, any attempts to resolve or enumerate users/groups provided
        only via glibc NSS is suppressed. If <option>--with-nss=yes</option> is specified, such users/groups
        are included in the output (which is the default).</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--with-varlink=<replaceable>BOOL</replaceable></option></term>

        <listitem><para>Controls whether to include Varlink user/group lookups in the output, i.e. those done
        via the <ulink url="https://systemd.io/USER_GROUP_API">User/Group Record Lookup API via
        Varlink</ulink>. If <option>--with-varlink=no</option> is used, any attempts to resolve or enumerate
        users/groups provided only via Varlink are suppressed. If <option>--with-varlink=yes</option> is
        specified, such users/groups are included in the output (which is the default).</para>

        <xi:include href="version-info.xml" xpointer="v249"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--with-dropin=<replaceable>BOOL</replaceable></option></term>

        <listitem><para>Controls whether to include user/group lookups in the output that are defined using
        drop-in files in <filename>/etc/userdb/</filename>, <filename>/run/userdb/</filename>,
        <filename>/run/host/userdb/</filename>, <filename>/usr/lib/userdb/</filename>. If
        <option>--with-dropin=no</option> is used, these records are suppressed. If
        <option>--with-dropin=yes</option> is specified, such users/groups are included in the output (which
        is the default).</para>

        <xi:include href="version-info.xml" xpointer="v249"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--synthesize=<replaceable>BOOL</replaceable></option></term>

        <listitem><para>Controls whether to synthesize records for the root and nobody users/groups if they
        are not defined otherwise, as well as the user/groups for the "foreign" UID range. By default (or with
        <literal>yes</literal>), such records are implicitly synthesized if otherwise missing since they have
        special significance to the OS. When <literal>no</literal>, this synthesizing is turned off.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>-N</option></term>

        <listitem><para>This option is short for <option>--with-nss=no</option>
        <option>--synthesize=no</option>. 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.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--multiplexer=<replaceable>BOOL</replaceable></option></term>

        <listitem><para>Controls whether to do lookups via the multiplexer service (if specified as true, the
        default) or do lookups in the client (if specified as false). Using the multiplexer service is
        typically preferable, since it runs in a locked down sandbox.</para>

        <xi:include href="version-info.xml" xpointer="v250"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--chain</option></term>

        <listitem><para>When used with the <command>ssh-authorized-keys</command> command, this will allow
        passing an additional command line after the user name that is chain executed after the lookup
        completed. This allows chaining multiple tools that show SSH authorized keys.</para>

        <xi:include href="version-info.xml" xpointer="v250"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--fuzzy</option></term>
        <term><option>-z</option></term>

        <listitem><para>When used with the <command>user</command> or <command>group</command> command, do a
        fuzzy string search. Any specified arguments will be matched against the user name, the real name of
        the user record, the email address, and other descriptive strings of the user or group
        record. Moreover, instead of precise matching, a substring match or a match allowing slight
        deviations in spelling is applied.</para>

        <xi:include href="version-info.xml" xpointer="v257"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--disposition=</option></term>

        <listitem><para>When used with the <command>user</command> or <command>group</command> command,
        filters by disposition of the record. Takes one of <literal>intrinsic</literal>,
        <literal>system</literal>, <literal>regular</literal>, <literal>dynamic</literal>,
        <literal>container</literal>. May be used multiple times, in which case only users matching any of
        the specified dispositions are shown.</para>

        <xi:include href="version-info.xml" xpointer="v257"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>-I</option></term>
        <term><option>-S</option></term>
        <term><option>-R</option></term>

        <listitem><para>Shortcuts for <option>--disposition=intrinsic</option>,
        <option>--disposition=system</option>, <option>--disposition=regular</option>,
        respectively.</para>

        <xi:include href="version-info.xml" xpointer="v257"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--uid-min=</option></term>
        <term><option>--uid-max=</option></term>

        <listitem><para>When used with the <command>user</command> or <command>group</command> command,
        filters the output by UID/GID ranges. Takes numeric minimum or maximum UID/GID values, respectively. Shows only
        records within the specified range. When applied to the <command>user</command> command, it matches
        against UIDs. When applied to the <command>group</command> command, matches against GIDs (despite the name of
        the switch). If unspecified, defaults to 0 (for the minimum) and 4294967294 (for the maximum), i.e. by
        default, no filtering is applied, as the whole UID/GID range is covered.</para>

        <xi:include href="version-info.xml" xpointer="v257"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--uuid=</option></term>

        <listitem><para>When used with the <command>user</command> or <command>group</command> command,
        filters the output to the record with the specified UUID. If unspecified, no UUID-based filtering is applied.</para>

        <xi:include href="version-info.xml" xpointer="v259"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--boundaries=</option></term>

        <listitem><para>When used with the <command>user</command> or <command>group</command> command,
        controls whether to show relevant UID/GID range boundary information in the tabular output. Takes a
        boolean. Defaults to true.</para>

        <xi:include href="version-info.xml" xpointer="v257"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>-B</option></term>

        <listitem><para>Shortcut for <option>--boundaries=no</option>.</para>

        <xi:include href="version-info.xml" xpointer="v257"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--from-file=PATH</option></term>
        <term><option>-F</option></term>

        <listitem><para>When used with the <command>user</command> or <command>group</command> command, read
        the user definition in JSON format from the specified file, instead of querying it from the
        system. If the path is specified as <literal>-</literal>, reads the JSON data from standard
        input. This is useful to validate and introspect JSON user or group records quickly, and check how
        they would be interpreted on the local system.</para>

        <xi:include href="version-info.xml" xpointer="v258"/></listitem>
      </varlistentry>

      <xi:include href="standard-options.xml" xpointer="no-pager" />
      <xi:include href="standard-options.xml" xpointer="no-legend" />
      <xi:include href="standard-options.xml" xpointer="help" />
      <xi:include href="standard-options.xml" xpointer="version" />
    </variablelist>
  </refsect1>

  <refsect1>
    <title>Commands</title>

    <para>The following commands are understood:</para>

    <variablelist>

      <varlistentry>
        <term><command>user</command> <optional><replaceable>USER</replaceable>…</optional></term>

        <listitem><para>List all known users records or show details of one or more specified user
        records. Use <option>--output=</option> to tweak output mode.</para>

        <para>If used in conjunction with <option>--from-file=</option> the user record data is read in JSON
        format from the specified file instead of querying it from the system. For details see above.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><command>group</command> <optional><replaceable>GROUP</replaceable>…</optional></term>

        <listitem><para>List all known group records or show details of one or more specified group
        records. Use <option>--output=</option> to tweak the output mode.</para>

        <para>If used in conjunction with <option>--from-file=</option> the group record data is read in JSON
        format from the specified file instead of querying it from the system. For details see above.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><command>users-in-group</command> <optional><replaceable>GROUP</replaceable>…</optional></term>

        <listitem><para>List users that are members of the specified groups. If no groups are specified, list
        all user/group memberships defined. Use <option>--output=</option> to tweak the output
        mode.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><command>groups-of-user</command> <optional><replaceable>USER</replaceable>…</optional></term>

        <listitem><para>Lists groups that the specified users are members of. If no users are specified, lists
        all user/group memberships defined (in this case, <command>groups-of-user</command> and
        <command>users-in-group</command> are equivalent). Use <option>--output=</option> to tweak the output
        mode.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><command>services</command></term>

        <listitem><para>List all services currently providing user/group definitions to the system. See below
        for a list of well-known services providing user information.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><command>ssh-authorized-keys</command></term>

        <listitem><para>Show SSH authorized keys for this account. This command is intended to be used to
        allow the SSH daemon to pick up authorized keys from user records, see below.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><command>load-credentials</command></term>
        <listitem>
          <para>When specified, the following credentials are used when passed in:</para>

          <variablelist>
            <varlistentry>
              <term><varname>userdb.user.*</varname></term>
              <term><varname>userdb.group.*</varname></term>
              <term><varname>userdb.transient.user.*</varname></term>
              <term><varname>userdb.transient.group.*</varname></term>
              <listitem>
                <para>These credentials should contain valid <ulink url="https://systemd.io/USER_RECORD">JSON
                User</ulink> and <ulink url="https://systemd.io/GROUP_RECORD">JSON Group</ulink> records. For
                <varname>userdb.user.*</varname> and <varname>userdb.group.*</varname> credentials, records
                are placed in <filename>/etc/userdb/</filename>, while for
                <varname>userdb.transient.user.*</varname> and <varname>userdb.transient.group.*</varname>
                credentials they are placed in <filename>/run/userdb/</filename>. These records implement the
                interface described in
                <citerefentry><refentrytitle>nss-systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
                Any passed user records must contain valid UID and GID fields. Any passed group records must
                contain a GID field (i.e. automatic UID/GID allocation is not supported). For both user and
                group records, the credential suffix (for <literal>userdb.user.foobar</literal> the suffix is
                <literal>foobar</literal>) must match the user or group name encoded in the record.</para>

                <xi:include href="version-info.xml" xpointer="v258"/>
              </listitem>
            </varlistentry>
          </variablelist>

          <xi:include href="version-info.xml" xpointer="v258"/>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1>
    <title>Well-Known Services</title>

    <para>The <command>userdbctl services</command> 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:</para>

    <variablelist>
      <varlistentry>
        <term><constant>io.systemd.DynamicUser</constant></term>

        <listitem><para>This service is provided by the system service manager itself (i.e. PID 1) and
        makes all users (and their groups) synthesized through the <varname>DynamicUser=</varname> setting in
        service unit files available to the system (see
        <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
        details about this setting).</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><constant>io.systemd.Home</constant></term>

        <listitem><para>This service is provided by
        <citerefentry><refentrytitle>systemd-homed.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
        and makes all users (and their groups) belonging to home directories managed by that service
        available to the system.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><constant>io.systemd.Machine</constant></term>

        <listitem><para>This service is provided by
        <citerefentry><refentrytitle>systemd-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
        and synthesizes records for all users/groups used by a container that employs user
        namespacing.</para>

        <xi:include href="version-info.xml" xpointer="v246"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><constant>io.systemd.Multiplexer</constant></term>

        <listitem><para>This service is provided by
        <citerefentry><refentrytitle>systemd-userdbd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
        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.
        <command>userdbctl</command> uses this service preferably, too, unless <option>--with-nss=</option>
        or <option>--service=</option> are used, in which case finer control over the services to talk to is
        required.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><constant>io.systemd.NameServiceSwitch</constant></term>

        <listitem><para>This service is (also) provided by
        <citerefentry><refentrytitle>systemd-userdbd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
        and converts classic NSS/glibc user and group records to JSON user/group records, providing full
        backwards compatibility. Use <option>--with-nss=no</option> to disable this compatibility, see
        above. Note that compatibility is actually provided in both directions:
        <citerefentry><refentrytitle>nss-systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 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.</para>

        <xi:include href="version-info.xml" xpointer="v245"/></listitem>
      </varlistentry>

      <varlistentry>
        <term><constant>io.systemd.DropIn</constant></term>

        <listitem><para>This service is (also) provided by
        <citerefentry><refentrytitle>systemd-userdbd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
        and picks up JSON user/group records from <filename>/etc/userdb/</filename>,
        <filename>/run/userdb/</filename>, <filename>/run/host/userdb/</filename>,
        <filename>/usr/lib/userdb/</filename>.</para>

        <xi:include href="version-info.xml" xpointer="v249"/></listitem>
      </varlistentry>

    </variablelist>

    <para>Note that <command>userdbctl</command> has internal support for NSS-based lookups too. This means
    that if neither <constant>io.systemd.Multiplexer</constant> nor
    <constant>io.systemd.NameServiceSwitch</constant> are running, look-ups into the basic user/group
    databases will still work.</para>
  </refsect1>

  <refsect1>
    <title>Integration with SSH</title>

    <para>The <command>userdbctl</command> 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 <citerefentry
    project='man-pages'><refentrytitle>sshd_config</refentrytitle><manvolnum>5</manvolnum></citerefentry>:</para>

    <programlisting>…
AuthorizedKeysCommand /usr/bin/userdbctl ssh-authorized-keys %u
AuthorizedKeysCommandUser root
…</programlisting>

    <para>Sometimes, it is useful to allow chain invocation of another program to list SSH authorized keys. By
    using the <option>--chain</option> option, such a tool may be chain executed by <command>userdbctl
    ssh-authorized-keys</command> once a lookup completes, regardless of whether an SSH key was found or
    not. Example:</para>

    <programlisting>…
AuthorizedKeysCommand /usr/bin/userdbctl ssh-authorized-keys %u --chain /usr/bin/othertool %u
AuthorizedKeysCommandUser root
…</programlisting>

    <para>The above will first query the userdb database for SSH keys, and then chain execute
    <command>/usr/bin/othertool</command> to also be queried.</para>
  </refsect1>

  <refsect1>
    <title>Exit status</title>

    <para>On success, 0 is returned, and a non-zero failure code otherwise.</para>
  </refsect1>

  <xi:include href="common-variables.xml" />

  <refsect1>
    <title>See Also</title>
    <para><simplelist type="inline">
      <member><citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>systemd-userdbd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>systemd-homed.service</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>nss-systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
      <member><citerefentry project='man-pages'><refentrytitle>getent</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
    </simplelist></para>
  </refsect1>

</refentry>