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

Over-specific method in api #11

Open
thomax opened this issue Sep 18, 2012 · 6 comments
Open

Over-specific method in api #11

thomax opened this issue Sep 18, 2012 · 6 comments
Labels

Comments

@thomax
Copy link

thomax commented Sep 18, 2012

No description provided.

@ghost ghost assigned bjoerge Sep 18, 2012
@thomax
Copy link
Author

thomax commented Sep 18, 2012

Copied from #2 (comment)
An :identity or :created_by parameter won't help, because someone could simply remove the parameter in order to see the email address or whatever.

This needs to be implemented by the policy/permissions system.

@thomax
Copy link
Author

thomax commented Sep 18, 2012

Copied from #2 (comment)
I think the idea here is to use the current_identity as a filter, not as a mean of access control.

@thomax
Copy link
Author

thomax commented Sep 18, 2012

Copied from #2 (comment)
But the email address would still be available if you get a bunch of posts (for the main view in dittforslag, for example), right?

@thomax
Copy link
Author

thomax commented Sep 18, 2012

Copied from #2 (comment)
Yes, but restrictions on who gets to see what should be enforced by a designated policy system. See also Simens comment on #7.

@thomax
Copy link
Author

thomax commented Sep 18, 2012

Copied from #2 (comment)
yeah, agreed. Conclusion is: we need to keep the dirty hack for now, and refactor when we implement the policy system :)

@thomax
Copy link
Author

thomax commented Sep 18, 2012

Copied from #2 (comment)
I believe this is also related to issue #58

@bjoerge bjoerge removed their assignment May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants