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
It seems the current logic will AND the listed required_groups.
For instance this would require the user to be in ALL 4 groups.
required_groups:
# If an array is given, the first element will be the attribute to check against, the second the group name
- ["memberOf", " CN=HD Admin,OU=Groups,OU=Corp,DC=test,DC=com"]
- ["memberOf", " CN=HD Helper,OU=Groups,OU=Corp,DC=test,DC=com"]
- ["memberOf", " CN=HD Reset,OU=Groups,OU=Corp,DC=test,DC=com"]
- ["memberOf", " CN=Security,OU=Groups,OU=Corp,DC=test,DC=com"]
It is desirable to check if a user belongs to ANY 1 of the groups listed to allow access by returning true to in_required_groups? if the user belongs to 1 or more of the listed groups.
Perhaps a separate YAML config option to control this behavior?
The text was updated successfully, but these errors were encountered:
Target cschiewek#149.
Should not be a breaking change since both the code and the documentation
clearly state that `required_groups` members either are strings,
or must have only two elements when any member is an array.
The feature here is that we can list a number of groups after the attribute
and at least any of them has to be matched to be able to pass the verification.
It seems the current logic will AND the listed required_groups.
For instance this would require the user to be in ALL 4 groups.
It is desirable to check if a user belongs to ANY 1 of the groups listed to allow access by returning
true
toin_required_groups?
if the user belongs to 1 or more of the listed groups.Perhaps a separate YAML config option to control this behavior?
The text was updated successfully, but these errors were encountered: