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

Proposal: Strict ACL validation such that agents can detect and reject unsupported ACLs #93

Closed
RubenVerborgh opened this issue Jul 28, 2020 · 3 comments

Comments

@RubenVerborgh
Copy link
Contributor

RubenVerborgh commented Jul 28, 2020

No description provided.

@justinwb
Copy link
Member

👍 to this. @RubenVerborgh can you confirm whether this use case supports this proposal, and/or whether you would see the need for expansion or adjustment?

@elf-pavlik
Copy link
Member

elf-pavlik commented Jul 29, 2020

I propose that agents should validate ACL documents against a strict shape before trying to enforce or modify them.a

I think currently the storage (Resource Server) enforces access control rules. We should avoid situations where storage would accept access control rules if it is not capable to fully enforce those rules. In that case only check on create (including restoring data from backup) or update seems needed.

@csarven
Copy link
Member

csarven commented Aug 7, 2020

This is part of a recurring issue. See solid/specification#169 . But I'm not sure if this panel is observing the issues in solid/specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants