Lines Matching refs:same

200 version of the record on the host, with the same four sections and augmented
221 users with the same name that originate in different organizations or
225 distinct from the same user in the `poettering.hq` realm. User records for the
226 same user name that have different realm fields are considered referring to
275 used when comparing two records of the same user to identify the newer one, and
633 is authorized to access the account. The strings should follow the same format
644 private key found on the same token. The resulting decrypted key is then
649 a matching one in `pkcs11TokenUri` and vice versa, with the same URI, appearing
650 in the same order, but this should not be required by applications processing
665 and `clientPin` booleans map to the FIDO2 concepts of the same name and encode
669 and vice versa, with the same credential ID, appearing in the same order, but
685 entry in either should map 1:1 to an entry in the other, in the same order and
703 which case all the object's setting should be applied. If the same option is
706 properties that are arrays themselves is done). If the same option is set in
720 within the same array entry, the object is honored when either match succeeds,
809 different things (see above). In contrast to the top-level field of the same