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

Add acl:TrustedApp #64

Open
timbl opened this issue Feb 1, 2022 · 2 comments
Open

Add acl:TrustedApp #64

timbl opened this issue Feb 1, 2022 · 2 comments
Assignees

Comments

@timbl
Copy link
Contributor

timbl commented Feb 1, 2022

This is used as a way in the Solid Authentication for a user to say that a given web app (origin) is trusted and should not be blocked by cross-site security.

@coolharsh55
Copy link

IMHO the term Trusted has much broader connotations than what is referred here (ref. turning off XSS protection), and once used in this manner, may be difficult to redefine. For example, to express an app is 'trusted' to always access/use some data in some way, or that it has passed some arbitrary conditions (e.g. set of guidelines, codes of conduct).

A better term may be OriginTrustedApp to explicitly denote the 'trust' is for the origin (which would point towards cross-site security).

@csarven csarven self-assigned this Oct 21, 2022
@csarven
Copy link
Member

csarven commented Oct 21, 2022

I came to the same conclusion based on my observation of its use in the community in that the "origin" part was sometimes overlooked or misapplied in the same way for acl:origin. I took that into account and tried to be clear in https://solidproject.org/TR/wac#web-origin-authorization FWIW.

I may be mistaken but I think Tim intended acl:trustedApp as a property instead of a class which is used by implementations but haven't yet made its way into the ACL Ontology.

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

No branches or pull requests

3 participants