Re: [pylons-discuss] Proper handling of views for ACL roles

2017-10-16 Thread Michael Merickel
> I understand your point of mutually exclusive roles for predicates, but seeing that `effective_principals` takes a list, I assume that I can use multiple roles for the predicate? Right, my point there is that sometimes it's by design in how the predicates work and sometimes it's on you as a user

Re: [pylons-discuss] Proper handling of views for ACL roles

2017-10-16 Thread jens . troeger
Thank you, Michael, exactly what I was looking for :-) I understand your point of mutually exclusive roles for predicates, but seeing that `effective_principals` takes a list, I assume that I can use multiple roles for the predicate? Cheers, Jens On Monday, October 16, 2017 at 11:04:56 AM UTC

Re: [pylons-discuss] Proper handling of views for ACL roles

2017-10-15 Thread Michael Merickel
It seems you're asking about how to affect the "view lookup" [1] phase of the request. https://docs.pylonsproject.org/projects/pyramid/en/1.9-branch/narr/router.html The "permission=" is not a predicate and thus cannot be used as part of view lookup to select between various views. The way to do

[pylons-discuss] Proper handling of views for ACL roles

2017-10-15 Thread jens . troeger
Hi, I'm using Cornice and Pyramid for my REST API server, and followed the standard authorization examples using ACLs