Lines Matching refs:field

112    object field we can easily remove it from view.
115    (an array field of the user record). Primarily these are resource
119    array comes with a `matchMachineId` or `matchHostname` field which indicate
214 UNIX user name. This field is the only mandatory field, all others are
215 optional. Corresponds with the `pw_name` field of of `struct passwd` and the
216 `sp_namp` field of `struct spwd` (i.e. the shadow user record stored in
228 version has to match in both `userName` and `realm` field. This field is
231 see above) with a user record without one set, even if the `userName` field matches.
234 user's real ("human") name, and corresponds loosely to the GECOS field of
236 record this field is initialized from GECOS (i.e. the `pw_gecos` field), and
237 vice versa when converting back. That said, unlike GECOS this field is supposed
238 to contain only the real name and no other information. This field must not
269 field, based on other fields, for example the numeric UID. By setting this
270 field explicitly applications can override this default determination.
274 `regular`, `privileged`, `perMachine` sections) was last changed. This field is
280 user was last changed. This corresponds to the `sp_lstchg` field of `struct
281 spwd`, i.e. the matching field in the user shadow database `/etc/shadow`,
285 this user. This corresponds with the `pw_shell` field of `struct passwd`, and
287 terminal log-in this field should not be set.
336 not log in. If this field is missing it should be assumed to be false,
337 i.e. logins are permitted. This field corresponds to the `sp_expire` field of
346 shall not be permitted anymore. This corresponds to the `sp_expire` field of
436 to during log-in. It corresponds to the `pw_dir` field of `struct passwd`.
439 use for the user.  This corresponds to the `pw_uid` field of `struct passwd`.
442 ID (GID) to use for the user. This corresponds to the `pw_gid` field of
532 user's password. By default the policy is enforced, but if this field is false
561 `sp_warn` field of `struct spwd`.
565 deactivated. This corresponds with the `sp_inact` field of `struct spwd`.
568 on next login. This corresponds with the `sp_lstchg` field of `struct spwd`
616 record top-level object, in the `privileged` field. Any data included in this
629 corresponds with `sp_pwdp` field of `struct spwd` (and in a way the `pw_passwd`
630 field of `struct passwd`).
663 `hashedPassword` field of the `fido2HmacSalt` field shall be a UNIX password
674 currently permitted value is the string `modhex64`. The `hashedPassword` field
683 keys should be accepted wherever regular passwords are. The `recoveryKey` field
684 should always be accompanied by a `recoveryKeyType` field (see above), and each
698 The `perMachine` field in the top-level object is an array of objects. When
708 here too no merging of individual fields is done, the later field always wins
750 user record that contains no `uid` field in the regular section is likely
809 different things (see above). In contrast to the top-level field of the same
810 (or the one in the `perMachine` section), this field reports the current size
823 field below). However, it is recommended to stick to a basic vocabulary here:
832 in which `state` lives, see above. Note that this field also exists on the
834 `regular` field should be used if conceptually the user record can only be
835 managed by the specified service, and this `status` field if it can
876 `stopDelayUSec` if the field is not explicitly specified: for home directories
897 The `signature` field in the top-level user record object is an array of
899 `key` (both are strings). The `data` field contains the actual signature,
900 encoded in Base64, the `key` field contains a copy of the public key whose
950 The `secret` field of the top-level user record contains the following fields:
955 for unlocking security tokens that require that. (The field `pkcs11Pin` should
956 be considered a compatibility alias for this field, and merged with `tokenPin`
1002 `pw_passwd` field in `struct passwd` is set to `"x"`, and the actual password
1003 is stored in the shadow entry `struct spwd`'s field `sp_pwdp`.
1012   appropriate for the data field.