feat(new-device): mint mTLS enrollment bundle, drop legacy .vagent UI #51
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/vapp-38-mtls-enrollment-bundle-ui"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rewrite the "+ New Device" dialog onto the agent's mTLS enrollment path (VA-67/VS-69). The dialog now mints a single-use enrollment bundle through a new session-forwarding
mint_enroll_bundleserver fn, which proxies vervain-server's session-gatedPOST /api/v1/enroll-tokensexactly like the old group-config proxy did, and renders the Linux x86_64 Option 2 one-liner (download the agent binary, then curl the one-time/api/v1/enroll-bundle?token=straight intovervain-agent install --system --from -), abootstrap.jsondownload with theinstall --from bootstrap.jsonsnippet for the out-of-band scp path, the bundle expiry, and a note that the agent mTLSdomainport differs from the HTTPS download host.The device-facing URLs target the browser/HTTPS listener at the agent
domain's host on the standard HTTPS port (the mTLS port thedomaincarries is dialed directly by the agent, VS-69); the binary download keeps its scoped install token (VS-57) so the unattended devicecurlis authorized.Remove the legacy enrollment surface: the
get_group_installproxy, the/groupsettings.ashxcall, theGroupServer/.vagent/config sealparsing helpers and their tests, and theGroupInstallmodel. A newcomponents::enroll_guardtest embeds the touched files and fails the build if any of those symbols reappear.list_groupsis intentionally kept: device groups remain a first-class feature (the groups page, the device-detail move control, and user group assignment all use it); only the enrollment dialog stopped selecting a group.#VAPP-38