Skip to main content

Give a node a new token

A node joins Jaah with a token, a secret that is shown only once. Give it a new one when the old one may have leaked, or when the machine lost it, for example after a reinstall. The old token stops working the moment you confirm, so the node goes offline until you run the new command on the machine.

There are two ways. Re-issue in the Machines list gives the node a new token. Re-enrol on the node's page does the same, and the new command also re-joins the node to your organization's network once. Use Re-enrol when the machine was rebuilt and lost its network place as well.

Who can do this: requires the org admin role (Org Owner or Admin). On a node whose settings are locked for your organization, neither item appears.

Re-issue a token from the list​

  1. In the sidebar, select Directory, then the Machines tab.
  2. Find the node's row and select ⋯ at its end.
  3. Select Re-issue.
  4. The dialog asks Re-issue this node’s token? Select Re-issue token.
  5. The New token for dialog shows the command. Select Copy, then run it on the machine. Paste it whole.
  6. Select I’ve copied it. The command is shown only once, and the dialog can't be opened again.
  7. Check the node's row: its status turns ONLINE once the machine reports with the new token.

Re-enrol a node from its page​

  1. In the sidebar, select Directory, then the Machines tab, and select the node's name.
  2. On the Overview tab, select Re-enrol in the row of actions. If the node has never connected, it is unavailable and reads Not connected yet.
  3. The dialog asks Re-enrol this node? Select Re-enrol.
  4. The Re-enrol dialog shows the command and a deadline: Run it before a date and time. Select Copy, then run it on the machine before then.
  5. Select I’ve copied it.
  6. Check the node's status on its page. It turns ONLINE once the machine reports again.

After either one, delete the command from the machine's shell history, as the dialog says. It holds the token.