Lines Matching refs:binding

125 4. Various fields are located in the `binding` section (a sub-sub-object of the
138    `binding` fields individually. Typically, the binding section is persisted
143    machine ID, similar to the way the `binding` section is organized). This
156    except for `regular`, `privileged`, `perMachine`. Specifically, `binding`,
178 | binding    | no                    | yes        | no                 | yes                       …
189 `perMachine` or `binding` sections and can include its data exclusively in the
201 with an additional, fifth `binding` section. When a local client enquires about
596 `binding` → An object, keyed by machine IDs formatted as strings, pointing
597 to objects that contain the `binding` section of the user record,
744 ## Fields in the `binding` section
746 As mentioned, the `binding` section contains additional fields about the user
751 extended with one in the `binding` section to assign a local UID if no global
754 All fields in the `binding` section only make sense in a local context and are
755 suppressed when the user record is ported between systems. The `binding` section
758 the information that `binding` is supposed to contain that binds the portable
761 The `binding` sub-object on the top-level user record object is keyed by the
762 machine ID the binding is intended for, which point to an object with the
765 both. Usually, the `binding` value should not contain settings different from
773 used already which is pinned in the `binding` section).
775 The following fields are defined in the `binding` section. They all have an
790 This section is arranged similarly to the `binding` section: the `status`
1051         "binding" : {
1104 file. This version lacks the `binding` and `status` sections which are used for