<term><varname>userdb.user.*</varname></term>
<term><varname>userdb.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 each matching
- credential, various files are created in <filename>/etc/userdb/</filename>, implementing the
- interface described in
+ <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
+ each matching credential, various files are created in <filename>/etc/userdb/</filename>,
+ implementing the interface described in
<citerefentry><refentrytitle>nss-systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- Any passed user records must contain uid and gid fields. Any passed group records must
- contain a gid field. 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>
+ 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>