You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
GatewayArea: what it touches
Internal ChangesKind: in v2.1.268,
ImprovementsSection of the release
Unclear What internalNetworks controls in the gateway setup flow is not specified by the finding.
What
The interactive gateway login flow (the device-code OAuth sign-in) now accepts a list of declared internal networks (internalNetworks) and resolves the gateway's host against that list before contacting the OAuth endpoint.
If the connection matches a declared network, the trust prompt shown to you now displays the actual network path, e.g. "Connecting from to , both inside declared ".
The gateway setup screen component was updated to accept this internalNetworks list as a new prop alongside the existing initialUrl and screenLocked props, so the wizard can be told about or restricted to these internal addresses.
Why
Seeing the concrete network path in the trust prompt makes it easier to verify a gateway connection is staying inside your organization's declared network rather than silently trusting an unfamiliar route.
