Max Connect
Max Connect · evidence atom

Legacy maxauth API authentication is replaced by API keys

MAXCONNECT-TECH-008 · TECH · amber · medium-high

← Pack hub

---

id: MAXCONNECT-TECH-008

title: Legacy maxauth API authentication is replaced by API keys

type: TECH

state: amber

area: F-feasibility

purpose: notebooklm-tier2-decomposition

priority: A

work_kind: A

provenance: research

confidence: medium-high

triangulated: true

engagement: maxconnect

sources:

- uri: file://notebooklm/answers/20260611T200650Z-01-product-workings.md

role: supporting

- uri: file://notebooklm/answers/20260611T200650Z-02-architecture-integrations.md

role: supporting

relates_to: []

feeds_atoms: []

open_questions: []

needs_validation: []

resolution_log:

- 2026-06-12: Decomposed from broad NotebookLM synthesis into pack-grade atom for Max Connect Discovery.

module:

---

Machine-to-machine and REST API interactions in MAS do not use the legacy maxauth method. Administrators must generate API keys and bind them to appropriate user-management or system-configuration privileges.

Amendment log