Lines Matching refs:of

13 Conceptually, much of what applies to JSON user records also applies to JSON
14 group records. They also consist of seven sections, with similar properties and
19 `groupName` → A string with the UNIX group name. Matches the `gr_name` field of
24 field of user records. A string in DNS domain name syntax.
27 `realName` field of user records, and accepts arbitrary strings, as long as
30 `disposition` → The disposition of the group, conceptually identical to the
31 same field of user records. A string.
37 epoch 1970) of the last time the group record has been modified. (Covers only
41 ID (GID) to use for the group. This corresponds to the `gr_gid` field of
44 `members` → An array of strings, listing user names that are members of this
47 the JSON group record, or in both. The list of memberships should be determined
48 as the combination of both lists (plus optionally others). If a user is listed
49 as member of a group and doesn't exist it should be ignored. This field
50 corresponds to the `gr_mem` field of `struct group` and the `sg_mem` field of
53 `administrators` → Similarly, an array of strings, listing user names that
54 shall be considered "administrators" of this group. This field corresponds to
55 the `sg_adm` field of `struct sgrp`.
65 `hashedPassword` → An array of strings with UNIX hashed passwords; see the
67 `sg_passwd` field of `struct sgrp` (and `gr_passwd` of `struct group` in a
76 equivalent to the fields of the same name in the `regular` section, and
84 to the fields of the same name in the `regular` and `perMachine` sections:
91 equivalent to the fields of the same name in the `regular` section, though with