Security and Configuration Boundaries
Understand AutoCore authentication, authorization, installation, edition, configuration, and external-service boundaries.
Authentication
The API identifies protected callers through the authentication/session boundary. The user model separates account identity from authentication identities and sessions. Anonymous public reads are deliberately narrower than authenticated or Admin operations.
Authorization
Role guards apply the hierarchical user, moderator, admin, and
super_admin roles. Permission guards apply fine-grained keys. Domain services
then check listing ownership, dealer membership, dealer role, resource state,
and edition/market context. Passing one guard does not replace the others.
Installation and edition
The explicit edition resolver must fail on unset or unknown values. Namespace checks keep databases, cookies, cache, queues, search, storage, ports, and deployment identity from being silently shared across editions. One installation has one primary market in Commercial 1.0.
External services
Storage, email, SMS, monitoring, search, and payment providers are external configuration boundaries. Credentials are environment references or provider secrets and are never public documentation values. A provider’s adapter or configuration row does not prove activation, approval, or successful delivery.
Security consequence
The reverse proxy limits exposure, but API authorization remains authoritative. Audit records support sensitive actions. Public documentation intentionally omits private topology identifiers, personal data, credentials, and production paths.