You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// audiences is the set of acceptable audiences the JWT must be issued to.
368
-
// At least one of the entries must match the "aud" claim in presented JWTs.
369
370
// Same value as the --oidc-client-id flag (though this field supports an array).
370
371
// Required to be non-empty.
371
372
Audiences []string`json:"audiences,omitempty"`
373
+
374
+
// audienceMatchPolicy defines how the "audiences" field is used to match the "aud" claim in the presented JWT.
375
+
// Allowed values are:
376
+
// 1. "MatchAny" when multiple audiences are specified and
377
+
// 2. empty (or unset) or "MatchAny" when a single audience is specified.
378
+
//
379
+
// - MatchAny: the "aud" claim in the presented JWT must match at least one of the entries in the "audiences" field.
380
+
// For example, if "audiences" is ["foo", "bar"], the "aud" claim in the presented JWT must contain either "foo" or "bar" (and may contain both).
381
+
//
382
+
// - "": The match policy can be empty (or unset) when a single audience is specified in the "audiences" field. The "aud" claim in the presented JWT must contain the single audience (and may contain others).
383
+
//
384
+
// For more nuanced audience validation, use claimValidationRules.
385
+
// example: claimValidationRule[].expression: 'sets.equivalent(claims.aud, ["bar", "foo", "baz"])' to require an exact match.
0 commit comments