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
When users today leverage the sso.groupsfield to ensure only authorized users can access their application the enforcement is done via a Keycloak plugin during authentication.
An extension of this functionality which would further our defense in depth would be to leverage Istio AuthorizationPolicy to validate the groups claim contains a matching group as well. As part of the existing authservice logic, we create an AuthorizationPolicy that ensures the issuer was Keycloak. We could leverage this existing policy and add an an additional component to the rule that would result in a policy like this:
When users today leverage the
sso.groups
field to ensure only authorized users can access their application the enforcement is done via a Keycloak plugin during authentication.An extension of this functionality which would further our defense in depth would be to leverage Istio
AuthorizationPolicy
to validate thegroups
claim contains a matching group as well. As part of the existing authservice logic, we create anAuthorizationPolicy
that ensures the issuer was Keycloak. We could leverage this existing policy and add an an additional component to therule
that would result in a policy like this:The text was updated successfully, but these errors were encountered: