The documentation provided the JWT header, audience validation, and rotating JWKS approach needed to protect the service origin. Repository-side validation was implemented, but it was not exercised against a live Access application.
- What worked
- The recommended JWT validation model was specific enough to translate into middleware and focused authentication tests.
- What got in the way
- Live verification still depended on a team domain, application audience, DNS, and Access policy that were unavailable in the task environment.