-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep ACL conditions as maps #3501
Commits on Jan 14, 2022
-
Update ACL logic, changing the conditions to maps
Functional changes: - More possibilities to combine rules - Domain check is now explicit with #{match => all} - Domain can't be 'global' anymore, because user's one can be passed instead with the same effect
Configuration menu - View commit details
-
Copy full SHA for b5f32b3 - Browse repository at this point
Copy the full SHA b5f32b3View commit details -
Do not convert configured ACL conditions from maps to tuples
Maps are now handled in acl.erl 'nodeprep' for all values is kept as it seems to be good enough.
Configuration menu - View commit details
-
Copy full SHA for 58379a2 - Browse repository at this point
Copy the full SHA 58379a2View commit details -
Use 'acl:match_rule' instead of 'acl:match_rule_for_host_type'
The name was updated as the functions were unified.
Configuration menu - View commit details
-
Copy full SHA for 0354274 - Browse repository at this point
Copy the full SHA 0354274View commit details -
Pass host type from pubsub to acl:match_rule
The module does not support dynamic domains yet, but the host type can be safely obtained from the server host.
Configuration menu - View commit details
-
Copy full SHA for cbd264e - Browse repository at this point
Copy the full SHA cbd264eView commit details -
Pass host type from c2s and commands to acl:match_rule
The host type can be safely obtained here.
Configuration menu - View commit details
-
Copy full SHA for 23497b4 - Browse repository at this point
Copy the full SHA 23497b4View commit details -
Add a version of 'match_rule' without the check for 'current_domain'
This is now used: - By s2s when the "user" is actually another server. - By components when the "server" is a component. In both cases the 'current_domain' check would never succeed, so the user would always have to add 'match = "all"' to the ACL.
Configuration menu - View commit details
-
Copy full SHA for 36f2894 - Browse repository at this point
Copy the full SHA 36f2894View commit details -
Configuration menu - View commit details
-
Copy full SHA for c4c6429 - Browse repository at this point
Copy the full SHA c4c6429View commit details -
Update config parser tests with the new ACL format
Expect the default 'match => current_domain' condition as well.
Configuration menu - View commit details
-
Copy full SHA for 1b16bc6 - Browse repository at this point
Copy the full SHA 1b16bc6View commit details -
Update small tests with the new ACL format
s2s tests need domain to host type resolution now
Configuration menu - View commit details
-
Copy full SHA for 9f503b1 - Browse repository at this point
Copy the full SHA 9f503b1View commit details -
Configuration menu - View commit details
-
Copy full SHA for c349533 - Browse repository at this point
Copy the full SHA c349533View commit details -
Remove the empty regexp from the 'local' ACL
It is not needed, the pattern is valid without it.
Configuration menu - View commit details
-
Copy full SHA for 7abeeef - Browse repository at this point
Copy the full SHA 7abeeefView commit details -
The main change is the default condition 'match = "current_domain"', which was implicit and hard to control before the changes.
Configuration menu - View commit details
-
Copy full SHA for 971e1c5 - Browse repository at this point
Copy the full SHA 971e1c5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 85bb20b - Browse repository at this point
Copy the full SHA 85bb20bView commit details