Skip to main content
Version: 1.7.0

API Token Agent Field and IP Magic Box User Agents Sync

Version: 1.7.0 Date: 2026-07-15

Goal: Support neo-backend agent validation on POST /api/v2/documents and track IP Magic Box client versions per user for ops dashboards.

Solution: Optional agent on apitokens (ops-managed). On magic-box / Azure token create or reuse, sync users.agent and users.agents.ipmagicbox alongside legacy boxVersion / currentJob.

Features:

  • apitokens.agent optional field (e.g. iptower for Tower)
  • users.agents.ipmagicbox runtime map updated on IP Magic Box login
  • No new admin HTTP endpoints in legacy backend

Implementation Details:

  • buildIpmagicboxUserUpdate() centralizes user document updates
  • Token reuse path (existing non-expiring magic-box token) also refreshes agent runtime

Files Modified:

  • app/database/schema/api-token.js - Optional agent field
  • app/database/schema/user.js - agents map on user schema
  • app/services/api-token.js - User sync on token create/reuse

Release fragment: feat-auto-attributes