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
{{ message }}
This repository was archived by the owner on Dec 7, 2020. It is now read-only.
I'm trying to get keycloak-proxy b73e8bd (current master) running against dex (with an LDAP backend) as an oidc provider. dex does not know about roles, but supports a groups claim, which may end up with a token like this:
Hi @ginkel ... I've raised a quick PR #301 which implements access controls on the groups claim as it's a useful feature and I know Keycloak now includes this claim as well. One thing, unlike the roles where the user requires all roles specified, groups are applied with an OR operation. This in my head made sense, but let me know your thoughts.
My use-cases are currently so simple that I typically only have a single group per resource, but I'm wondering why the behavior should be different from that of other claims that all need to be satisfied for an access to be permitted.
This is more of a question than an issue.
I'm trying to get keycloak-proxy b73e8bd (current master) running against dex (with an LDAP backend) as an oidc provider. dex does not know about roles, but supports a
groups
claim, which may end up with a token like this:Is there a way in keycloak-proxy to express a claim match that only permits access if the group
app-group
is present in thegroups
claim?Thanks!
The text was updated successfully, but these errors were encountered: