Skip to content

History / Web App Integration Spec

Revisions

  • Integration spec: state /me's main purpose Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    Ben Siler committed Oct 28, 2026
  • Integration spec: reviewer feedback (exemptions, forwarding, headers, kid) - /healthz is the default exemption; others only with admin approval - forward the token only to backend services that are part of the app - don't trust any request header, whatever its name; ask admins for others - verify once app-wide, then authorize per route as needed - reading the kid is fine; never take a key or key URL from the token - 'no authentication secrets'; /me states its purpose Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    Ben Siler committed Oct 27, 2026
  • Integration spec: JWKS URL uses the full (sharded) Twingate address The short <network>.twingate.com form can redirect to the regional shard, and some JWT libraries (jose) refuse to follow redirects, so the app could never load keys. Admins now copy the Admin Console address exactly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    Ben Siler committed Oct 21, 2026
  • Integration spec: hyphenate natural-language, strip trailing spaces Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    Ben Siler committed Oct 21, 2026
  • Updated instructions for admins for additional clarity

    @bens-twingate bens-twingate committed Oct 21, 2026
  • Add Web App integration spec for coding agents A page admins copy, fill in and hand to the coding agent building an internal web app behind the Gateway: verify the GAT on every request in one app-wide check, bind it to the network and the resource, fail closed, and test it with locally generated keys. Linked from the sidebar under Web App. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    Ben Siler committed Oct 21, 2026