Skip to content

Add SCO re-onboarding step to ensure no authorized keys escape cleanup #1120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Chr1st0ph3rTurn3r merged 1 commit into from
Aug 19, 2026
Merged

Add SCO re-onboarding step to ensure no authorized keys escape cleanup #1120

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion docs/sec-conductor-onboard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,27 @@ Mon 2026-08-10 18:29:06 UTC

```

3. Restore the original asset ID.
3. Ensure all authorized keys are removed for the original asset ID.

`delete system connectivity authorized-keys entry comment <asset-id> node all`

This operation may indicate keys were removed.

```
admin@node0.Conductor# delete system connectivity authorized-keys entry comment Spoke1Node0 node all
✔ Updating SSH Configuration...
Deleted 2 entries on node0.Conductor
```

Alternatively, the keys may have been missing or removed by the temporary asset rename. It is **not an issue** if no entries are removed.

```
admin@node0.Conductor# delete system connectivity authorized-keys entry comment Spoke1Node0 node all
✔ Updating SSH Configuration...
Deleted 0 entries on node0.Conductor
```

4. Restore the original asset ID.

`config authority router <router> node <node> asset-id <asset-id>`

Expand Down