corestack_ ssh_ legacy_ key_ keep
Keep a Legacy SSH key.
When to use it
Keep a Legacy key (from corestack_ssh_legacy_list) so it still works after the old shared list ends: at an environment, website or company (it logs in as web), or as your own personal key (user with your id). Long-running.
Ask for it
Using the Corefinity MCP server, call corestack_ssh_legacy_key_keep with key_id 80211, owner {"type":"company","id":4211}. (Keep a Legacy SSH key.) Tell me what it returned.Inputs
key_idintegerRequired
A Legacy key's id (corestack_ssh_legacy_list). At least 1.
ownerobjectRequired
{type, id} — where to keep it.
Fields
idintegerRequired
At least 1.
typestringRequired
environmentwebsitecompanyuserExample call
{
"name": "corestack_ssh_legacy_key_keep",
"arguments": {
"key_id": 80211,
"owner": {
"type": "company",
"id": 4211
}
}
}If it is refused
| Reason | What to do |
|---|---|
managed_elsewhere | Another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done. |
forbidden | Keeping the key as a company's key and the person's role lacks the Create Company SSH Keys permission. The message names it and says an owner of the company can grant it in Roles; details.permission is createCompanySSHKeys. Nothing is changed. |
switched_off | SSH keys are not switched on for this object yet. |
ssh_not_legacy | The key is not a Legacy key. |
ssh_legacy_ended | The Legacy list has already ended. |
ssh_managed_on_another_environment | This CoreStack Enterprise environment runs on the same server as another environment whose SSH the Control Panel manages, so its own keys are added, changed and removed there; the refusal's managed_on names that environment ({id, name}). |
enterprise_panel_only | SSH keys for CoreStack Enterprise environments are managed in the Control Panel only at the moment. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The same task elsewhere
Was this helpful?