Manage submission tokens
Issue, rotate and revoke the per-team tokens that identify a team when it submits flags.
Teams submit flags to a network endpoint, usually from an automated exploit farm. Because many teams can reach that endpoint from the same address, a team is identified by its submission token, not by where it connects from. The token is the first line a farm sends; see the player guide’s Submit flags from a farm.
Issue a token
Open Teams, select a team and find Submission token. Click Issue new generation and confirm; the newest token then appears there and on the team’s Downloads page. From the command line: athena ad team token-issue.
A team without a live token can’t submit flags; its Downloads page says so.
Rotate a token
Issuing a new generation is how you rotate a token. Earlier generations keep working until you revoke each one, so a team can move its farm to the new token without losing submissions. Give the team the new value, then revoke the old generation once it has switched.
See every live generation
Submission token lists every live generation of the team’s token: its number, whether it is the newest, and when a farm last used it. athena ad team tokens prints the same list, with each generation’s hash.
Revoke a generation
Click Revoke next to a generation and confirm, or run athena ad team token-revoke with the hash athena ad team tokens prints. The token stops working immediately, including for a farm already connected: its next flag is answered Invalid team token: revoked and the connection closes. A revoked generation is never issued again.
Revoking one generation leaves the others live. To stop a team submitting altogether, revoke every generation. The team can submit again once you issue a new one.
When a player leaves
A submission token belongs to the team, not to a player, so removing or banning a player doesn’t change it. If the player knew the token, issue a new generation, give it to the team and revoke the old one.