api config: Refactor jwt_auth filter config#3428
api config: Refactor jwt_auth filter config#3428nickrmc83 wants to merge 1 commit intoenvoyproxy:masterfrom
Conversation
This is the first in a series of PRs for introducing OpenID Connect and Session Management filters to envoy. Refactor jwt_auth filter config to aid re-usability of the JWT verification code in new OIDC filter. Added initial OpenID Connect Filter config defintions. These are subject to change. Design drafts and previous discussion from the istio-sec WG: - https://docs.google.com/document/d/1mGpUsRgmA9wPB73trfTiB9YUuwYh-31iulYg9USxe0Y/edit?usp=sharing - https://docs.google.com/document/d/1oRoHt0iDBYRd_ETEtGJiNLhV1dKWMNgC6EvZAGmNcgk/edit?usp=sharing Signed-off-by: Nick A. Smith <nick.a.smith@thales-esecurity.com>
| @@ -0,0 +1,243 @@ | |||
| syntax = "proto3"; | |||
|
|
|||
| package envoy.config.filter.http.common.v1alpha; | |||
There was a problem hiding this comment.
super quit drive by nit: Please put this in a more specific namespace/file/directory than "envoy.config.filter.http.common.v1alpha"
|
Hi @nickrmc83 The jwt_authn config is here now I also have a PR: #3381 Please rebase your change to them |
|
Looks like this hasn't been touched in a bit. Nick, any objection if we close this off for now, and you can reopen when it's ready for another look? |
|
Yeah no problem.
…On Tue, 29 May 2018, 14:47 alyssawilk, ***@***.***> wrote:
Looks like this hasn't been touched in a bit. Nick, any objection if we
close this off for now, and you can reopen when it's ready for another look?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3428 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhXUPpwM-TKB1yPjhXLDkEbNrj5ZgqNks5t3VFcgaJpZM4UDzEo>
.
|
|
Hi @nickrmc83 I was wondering where this was at. Are you still working on this? We are also interested in introducing OIDC to Envoy. |
|
Yes, this is still alive and being worked on in the istio security working
group but this PR is dead. #4242 is
an initial enabler for further pull requests. If you're interested I'd
encourage participation in the istio security WG.
…On Fri, 31 Aug 2018, 14:55 David Adams, ***@***.***> wrote:
Hi @nickrmc83 <https://github.com/nickrmc83> I was wondering where this
was at. Are you still working on this? We are also interested in
introducing OIDC to Envoy.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3428 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhXUDA9uKbhfeLh4h4gIv10blIZBpinks5uWUA4gaJpZM4UDzEo>
.
|
|
And https://github.com/ThalesIgnite/proxy/tree/gitlab/src/envoy/http/oidc is a PoC implementation that is being productized |
|
@nickrmc83 Thank you. |
Signed-off-by: Nick A. Smith nick.a.smith@thales-esecurity.com
Description:
This is the first in a series of PRs for introducing OpenID Connect (OIDC) and Session Management filters to envoy. The primary goal of this PR is to split the istio jwt_authn filter's configuration API in two. The reason for this is to isolate the JWT verification code from the forwarding rules thus making it easier to re-use the verification logic in multiple filters.
Refactor jwt_auth filter config to aid re-usability of the JWT verification code in new OIDC filter.
Added initial OpenID Connect Filter config defintions. These are subject to change.
Design drafts and previous discussion from the istio-sec WG:
Risk Level: Medium
Testing:
NA
Docs Changes:
None