YueGuobin 3d6d9a3396
fix(mcp): thread token_version into console/download token minting
Token revocation is a strict version check (token_data.token_version !=
user.token_version). create_access_token defaults token_version to 0, so the
short-lived JWTs minted for the console WebSocket URL (nodes) and the download
URLs (symbols, links) carried ver=0. Any user who had logged out at least once
(token_version >= 1, e.g. the default admin) got tokens rejected as "revoked"
on first use.

e433991cf fixed this in _resolve_token's API-key branch but missed these three
independent minting sites. Now resolve token_version during _resolve_token (the
JWT branch decodes it, the API-key branch reads user.token_version), carry it
through gns3_ctx, and pass it at every minting call.
2026-07-16 00:51:45 +08:00
..
2026-07-08 18:45:07 +02:00
2026-06-16 23:04:05 +08:00
2026-04-04 19:55:13 +08:00
2026-07-09 08:40:05 +02:00
2024-04-22 18:51:29 +07:00
2026-07-09 10:40:38 +02:00
2022-01-19 22:28:36 +10:30
2026-07-10 10:01:35 +02:00