Bundled trimble-connect OAuth client is a placeholder (AWARE_AECO_PLACEHOLDER_TRIMBLE_CLIENT_ID) — --oauth fails 'Unregistered client'

[pawellisowski]

Environment

• Windows, aware 0.44.0 (npm), bundled first-party OAuth apps (Ship a registered OAuth app + bundled client IDs so aware connect --device-code/--oauth works for end users #141 / feat(connect): ship registered M365 + Google OAuth apps (#141) #145).

Repro

aware connect trimble-connect --oauth

The browser opens to:

https://id.trimble.com/oauth/authorize?response_type=code
  &client_id=AWARE_AECO_PLACEHOLDER_TRIMBLE_CLIENT_ID
  &redirect_uri=http://localhost:7421/callback
  &scope=openid+profile+TrimbleConnect&code_challenge=...

Trimble responds:

{"error": "invalid_client", "error_description": "Unregistered client."}

Root cause

The bundled Trimble client_id is the literal placeholder string AWARE_AECO_PLACEHOLDER_TRIMBLE_CLIENT_ID, not a registered Trimble Identity OAuth client. #145 shipped real first-party clients for microsoft-365 and google-workspace (both connect end-to-end via --oauth), but trimble-connect was left as a placeholder, so its authorize request is rejected.

Impact

trimble-connect cannot be connected at all with the bundled app — neither --oauth (placeholder → Unregistered client) nor --device-code (Trimble doesn't support device-code; correctly rejected). The only path today is a BYO profile (#146) with the user's own registered Trimble client.

Ask

Ship a real registered Trimble Identity OAuth client for trimble-connect (as was done for M365/Google in #145), or — if a first-party Trimble app isn't available — make aware connect trimble-connect fail fast with a clear message ("no bundled Trimble app; configure a BYO profile, see #146") instead of sending a placeholder client_id to Trimble.

Related

• feat(connect): ship registered M365 + Google OAuth apps (#141) #145 (bundled M365 + Google apps), Tier 2: first-class bring-your-own OAuth app registration (per-org) #146 (BYO OAuth profiles), google-workspace --device-code surfaces a raw Google 401 instead of cleanly rejecting like trimble-connect does #151 (Google device-code 401).

[pawellisowski]

Verified fixed in v0.45.0 (PR #155). aware connect trimble-connect --oauth now fails fast: error: validation failed: trimble-connect has no bundled OAuth app yet — register your own and configure a BYO profile at ~/.aware/oauth/trimble-connect.yaml (see 10-core/oauth-registration.md, #146) — no placeholder client_id sent to Trimble. (A real first-party Trimble client is still the eventual fix; BYO profile works today.)