magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
1 min read

MGS9006: token not found

magus config console token revoke, magus config mcp connector revoke or the console's token settings named a token that the store does not contain.

[MGS9006] auth: no token has the name or id "ci"
  see: .../MGS9006.md

Why

Revoke takes an exact id when what you named is eight hex digits, and an exact name otherwise. No name may look like an id, so the two never mix, and nothing matches by prefix: a revoke deletes the token you named or nothing. Both commands read the one store, so either revokes any stored token. Nothing matched: the id or name is wrong, or it was already revoked or expired.

Resolution

List what is there and revoke by an exact id or name from the list:

magus config console token ls
magus config console token revoke <id-or-name>

What this is NOT

  • Not the operator token. It is not in the store and is never a revoke target here; rotate it with magus config token generate --force.

See also

MGS9006authconnectorconsoletokenrevokeid
Last updated (f0d4ffc9)
Earlier changes on this page (2)

Full history ↗ · Blame source ↗

Glossary

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. See targets.

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). See operations.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.