Skip to content
This repository has been archived by the owner on Feb 6, 2022. It is now read-only.

Passing auth result (client identity) to the backend / the next hop #96

Open
myidpt opened this issue May 8, 2017 · 0 comments
Open
Assignees
Milestone

Comments

@myidpt
Copy link

myidpt commented May 8, 2017

This requires Envoy to forward auth results to next hop. It is tracked by:
envoyproxy/envoy#794
After that, Istio should configure:

  1. For Side-car proxies, they always forward auth result to the backend.
  2. For cluster ingress controllers, when external service uses mTLS to call ingress controllers, the latter always forwards the auth result of to the next hop.
@myidpt myidpt added the P2 label May 8, 2017
@myidpt myidpt added this to the auth beta milestone May 8, 2017
@myidpt myidpt self-assigned this May 8, 2017
@geeknoid geeknoid removed the P2 label Jun 22, 2017
@wattli wattli modified the milestones: Istio 0.2, Istio 0.3 Sep 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants