Repository navigation
RivetMSP 26.10.24: the Remote button finds the device (MeshCentral node ids)
·
497 commits
to master
since this release
[26.10.24] RivetMSP — the Remote button finds the device (MeshCentral node ids)
Deploy notes: back up the database, pull this tag, run the database update (Administration > Updates or php scripts/update_cli.php --update_db). RivetCore is now 1.0.0-rc.18 (the tracked vendor/rivet/rivet-core is the tag's git archive, so no composer install is needed). DB 2.6.95: Core migration 0027_rmm_mesh_node_ids rewrites the stored MeshCentral node ids to one form (data only, no schema change, idempotent). No cron change.
- Bug fixed: Remote opened the MeshCentral home page instead of the device. MeshCentral finds a device by its 64-character id (
...?viewmode=11&gotonode=<64 characters>), but the agent reports the same 48 bytes as 96 hex characters and the link carriednode//<hex>. The link is now<mesh>/?login=<token>&gotonode=<64 characters>&viewmode=11&hide=31; every stored form is converted when the link is built, so it works even before the database update. - Paste whatever you have. The MeshCentral node field (Remote card, legacy device page) accepts the address bar of the device in MeshCentral,
node//..., the 64 characters aftergotonode=, or 96 hex characters, and showsnode//plus 64 characters. Help text: "In MeshCentral open the device and copy the address bar, or paste the node id." - Same node, one mapping. An agent that reports the node in hex and a hand-typed 64-character id are the same node: conflict detection compares them as such.
- Not verified on a live MeshCentral with this exact link; the shape is the one MeshCentral shows in its own address bar.
- Tests:
tests/rmm_ui_p68_remote.php(the launch URL carries the 64-character form for a device stored with the hex id, on every view; a pasted address is saved canonical),tests/wave1_integration.php(the 2.6.95 step, the rc.18 pin),tests/browser/rmm_rc17_remote_smoke.mjsextended.