Skip to content
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

policy: evaluate wildcard matching strategy #580

Closed
aeneasr opened this issue Sep 15, 2017 · 1 comment
Closed

policy: evaluate wildcard matching strategy #580

aeneasr opened this issue Sep 15, 2017 · 1 comment
Labels
feat New feature or request.
Milestone

Comments

@aeneasr
Copy link
Member

aeneasr commented Sep 15, 2017

One issue with access control policies is that, at the moment, we have the burden of regular expression overhead. This implies that scalability is limited.

Most matches however require simple wildcard logic, like resources:* or users:*:emails. It should be explored if wildcard matches perform better in memory and in databases and decided if regexp matching will be replaced with wildcard matching, or at least complemented.

@aeneasr aeneasr added feat New feature or request. policy labels Sep 15, 2017
@aeneasr aeneasr added this to the 1.0.0-alpha2 milestone Sep 15, 2017
@aeneasr aeneasr modified the milestones: 1.0.0-alpha1, unplanned Jan 15, 2018
@aeneasr aeneasr modified the milestones: unplanned, 1.0.0 Feb 9, 2018
@aeneasr aeneasr modified the milestones: 1.0.0, 1.0.0-alpha.1 Apr 19, 2018
@aeneasr
Copy link
Member Author

aeneasr commented May 20, 2018

This is now up to keto/ladon, see ory/keto#11

@aeneasr aeneasr closed this as completed May 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request.
Projects
None yet
Development

No branches or pull requests

1 participant