-
Notifications
You must be signed in to change notification settings - Fork 130
Open
Labels
epicRepresents an epic. Contains sub-issuesRepresents an epic. Contains sub-issues
Milestone
Description
As a cluster operator using NGF
I want to block any traffic without a valid JWT on the request
So that I can ensure all of my traffic on my authenticated endpoints are authenticated.
Background
As our first pass at authentication and authorization, we want to provide a first-class mechanism to validate JSON Web Tokens using a local key or from a jwks endpoint. This is a big API Gateway use case especially for larger organizations using NGINX Plus as authentication is most often performed at the "edge" of the application boundary.
Not included in this epic:
- JWT Authorization - validating specific fields or scopes within a JWT
- OpenID Connect Support (yet)
Acceptance Criteria
- NGF users are able to add a filter for HTTPRoutes for JWT authentication specifying a either a public key or a jwks endpoint.
- Any http/https requests that match for the
HTTPRoute
with enabled JWT authentication are validated against the configured JWT keys and rejected if the JWT fails validation.
Metadata
Metadata
Assignees
Labels
epicRepresents an epic. Contains sub-issuesRepresents an epic. Contains sub-issues
Type
Projects
Status
🆕 New