Solo.io’s JWTs for Service Auth Break API Gateways, by Christian Posta and Peter Jausovec, makes a point about internal traffic that’s easy to lose sight of. A team offloads authentication, authorization and throttling to the gateway for north/south traffic. Then it uses JWTs for service-to-service calls, and all of that work has to be rebuilt in every service and every language. The post sets out what “rebuilt” means: encrypted transport, checks on exp, iat, nbf and above all aud, a different token for each service called, rotation of the token service’s public keys, and expirations of “ideally just a couple of minutes.” The sharpest line explains why it matters: “JWTs send the sensitive bearer token material over the wire, while mTLS does not.”
This is a vendor arguing for the category it sells, and the conclusion follows: a service mesh for east/west traffic, the gateway for north/south. The technical case doesn’t depend on that conclusion, though. A wildcard or missing aud claim, hour-long expirations and long-lived client credentials sent on every refresh are all real failure modes, whatever terminates your TLS. A team that never adopts Istio can still use the post as a checklist.
The Solo.io provider page records 15 API pages. The ones that touch this story are the credential surfaces of the developer portal: the Solo.io Auth API, the Solo.io OAUTH Credentials API and the Solo.io API Keys API. These are where client credentials and keys are issued for the traffic the gateway protects. The mesh the post recommends, Solo Enterprise for Istio, is in the catalog description, but as a product rather than an API contract. That is the same gap our earlier coverage of Solo.io found: the catalog sees the portal more clearly than the gateway and mesh.
On the Kin Score, Solo.io measures 60.4, in the strong band. Developer ergonomics carries it at 78.6 and discoverability at 76.7. Contract governance is 28.0. Agent Readiness is 34.8, rated agent-ready, with auth clarity, error semantics and an MCP server lit. The unlit dimensions are the ones this post argues about: delegated identity, protected resource metadata and dynamic client registration. Those are the published, standard ways for a caller to learn how a resource wants to be authenticated. The post explains in careful detail how token audiences should work, and the catalog finds no machine-readable statement of how Solo.io’s own resources expect to be called.