wendy device enroll
Enrolls the connected device with Wendy Cloud (or a local pki-core) and provisions it with mTLS certificates.
wendy device enroll
Enrolls the connected device with Wendy Cloud (or a local pki-core) and provisions it with mTLS certificates.
Note:
wendy device enrollis an advanced command and is not listed inwendy device --help. It remains fully functional. For most setups, usewendy device setupinstead.
Usage
wendy device enroll [--name <name>] [--cloud-grpc <endpoint>] [flags]Description
wendy device enroll creates an enrollment token using your stored auth session, then has the connected agent fetch its certificate. Run wendy cloud login first.
› Certificate identity: The CSR submitted during provisioning includes the
› device's authoritative Wendy identity as a URI Subject Alternative Name
› (urn:wendy:org:‹org›:asset:‹assetID›). The cloud certificate service
› validates this SAN against the enrollment token at issuance time.
The enrolled device is registered in Wendy Cloud under a human-readable name. The name can be changed later with wendy device rename, so the command resolves it as follows:
-
--name <name>— always wins when provided. -
Hostname default — when
--nameis omitted and the device is reachable by hostname (e.g.playful-reed.local), the name defaults to that hostname with any.localsuffix stripped (soplayful-reed.local→playful-reed). -
Interactive prompt — in a terminal, when no
--nameis given the command prompts for a name. When a hostname default is available it is shown in brackets and used if you press Enter without typing anything:Device name [playful-reed]: -
Bare IP / no hostname — when the device is addressed by a bare IP (no resolvable hostname) and
--nameis omitted, there is no default. In a non-interactive environment this fails with:device name is required; pass --name when not running interactivelyIn an interactive terminal it prompts for a name with no default and errors if you leave it blank.
Naming an unnamed device: A device enrolled without a usable name shows up with an empty name in
wendy cloud discover. You can still address it by its numeric asset ID — seewendy cloud tunnel --device <id>.
Flags
| Flag | Default | Description |
|---|---|---|
--name | hostname (.local stripped) | Human-readable device name. Defaults to the device hostname when omitted; required when the device is reachable only by a bare IP address in a non-interactive environment. |
--cloud-grpc | "" | Cloud / pki-core gRPC endpoint to use. Overrides session selection; when omitted, the persisted default (set with wendy auth use) is used if available, otherwise an interactive picker appears. |
Examples
Enroll, defaulting the name to the device hostname:
wendy device enroll --device playful-reed.localEnroll with an explicit name:
wendy device enroll --device 192.168.1.11 --name lab-pi-01Related
wendy install→ Linux Desktop — mint a short-lived enrollment token and embed it in theagent.shone-liner so the device self-enrolls on first startup, without needing a USB connection or a running agent.wendy device setup— interactive wizard that provisions, configures WiFi, and enrolls in one flow.wendy cloud enroll-device— alias for this command, reachable through the cloud tunnel.wendy device provision— enroll against a self-hosted pki-core instead of Wendy Cloud.wendy device unenroll— reverse enrollment and delete the device from Wendy Cloud.