The gateway now tells you which configured sections do nothing because sign-in was never set up.
What's wrong with this entry?
If the gateway runs without OIDC it can never mint a session JWT, which silently disables managed policies, admin spend limits and telemetry forwarding. The gateway now names exactly which of those configured sections are inert and suggests either removing them or configuring OIDC.
oidc is not configured (CRI-only deployment), so no gateway session JWT can ever be minted
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway
-
v2.1.229
Gateway streaming keeps connections alive with pings
Both mention gateway
-
v2.1.232
Cloud gateway sign-in explains its restart, and refuses when it cannot
Both mention gateway