RequestAuthentication
RequestAuthentication
RequestAuthentication defines what request authentication methods are supported by a workload.If will reject a request if the request contains invalid authentication information, based on theconfigured authentication rules. A request that does not contain any authentication credentialswill be accepted but will not have any authenticated identity. To restrict access to authenticatedrequests only, this should be accompanied by an authorization rule.Examples:
- Require JWT for all request for workloads that have label
app:httpbin
apiVersion: security.istio.io/v1beta1
kind: RequestAuthentication
metadata:
name: httpbin
namespace: foo
spec:
selector:
matchLabels:
app: httpbin
jwtRules:
- issuer: "issuer-foo"
jwksUri: https://example.com/.well-known/jwks.json
---
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
name: httpbin
namespace: foo
spec:
selector:
matchLabels:
app: httpbin
rules:
- from:
- source:
requestPrincipals: ["*"]
- The next example shows how to set a different JWT requirement for a different
host
. TheRequestAuthentication
declares it can accpet JWTs issuer by eitherissuer-foo
orissuer-bar
(the public key set is implicitlyset from the OpenID Connect spec).“`yamlapiVersion: security.istio.io/v1beta1kind: RequestAuthenticationmetadata:name: httpbinnamespace: foospec:selector:matchLabels:app: httpbinjwtRules:- issuer: “issuer-foo”
- issuer: “issuer-bar”—apiVersion: security.istio.io/v1beta1kind: AuthorizationPolicymetadata:name: httpbinnamespace: foospec:selector:matchLabels:app: httpbinrules:
- from:
- source:requestPrincipals: [“issuer-foo/*”]to:hosts: [“example.com”]
- from:
- source:requestPrincipals: [“issuer-bar/”]to:hosts: [“another-host.com”]
- You can fine tune the authorization policy to set different requirement per path. For example,
yamlapiVersion: security.istio.io/v1beta1kind: AuthorizationPolicymetadata:name: httpbinnamespace: foospec:selector:matchLabels:app: httpbinrules:- from:- source:requestPrincipals: [””]- to:- operation:paths: [“/healthz]“`
to require JWT on all paths, except /healthz, the sameRequestAuthentication
can be used, but the
authorization policy could be:
Field | Type | Description | Required |
---|---|---|---|
selector | WorkloadSelector | The selector determines the workloads to apply the RequestAuthentication on.If not set, the policy will be applied to all workloads in the same namespace as the policy. | No |
jwtRules | JWTRule[] | Define the list of JWTs that can be validated at the selected workloads’ proxy. A valid tokenwill be used to extract the authenticated identity.Each rule will be activated only when a token is presented at the location recorgnized by therule. The token will be validated based on the JWT rule config. If validation fails, the request willbe rejected.Note: if more than one token is presented (at different locations), the output principal is nondeterministic. | No |