When a request is made by a component to a URL that is 'inside' the same namespace, it is important the JWT of the incoming request to the component be forwarded in the outgoing request. By contrast, if the request is going outside the namespace, it is important that the JWT is not forwarded—we must not forward valid JWT tokens to potentially-bad guys. In addition, if the call is staying within the namespace, it should really get short-circuited through Jeremy's "internal router" or the "ingress" rather than going back out to the internet and then back in.
We need a strategy for how all calls are made that originate within a namespace. Programming library? Forward-proxy? Other? Whatever the strategy, it needs to handle internal cals, external calls, and calls that could potentially be either.
When a request is made by a component to a URL that is 'inside' the same namespace, it is important the JWT of the incoming request to the component be forwarded in the outgoing request. By contrast, if the request is going outside the namespace, it is important that the JWT is not forwarded—we must not forward valid JWT tokens to potentially-bad guys. In addition, if the call is staying within the namespace, it should really get short-circuited through Jeremy's "internal router" or the "ingress" rather than going back out to the internet and then back in.
We need a strategy for how all calls are made that originate within a namespace. Programming library? Forward-proxy? Other? Whatever the strategy, it needs to handle internal cals, external calls, and calls that could potentially be either.