Re: ZEO authorization model?

> On May 25, 2016, at 08:46, Jim Fulton <[email protected]> wrote:
> 
> 
> I'm curious what other people think.  Does anyone else have desires
> for a ZEO authorization model? If so, what sort of requirements would
> you have?

I've personally never had a requirement for authorization (as distinct from authentication)---I write webapps---but it's an interesting concept.

> I was thinking that the
> access control would be pluggable and would moderate load, create and
> update operations.

I'm curious what you were thinking there. Would it operate at the level of the pickled bytes and OID? It seems to be that's not very much context to make decisions on. Unless the plugin was to unpickle each object? Aside from the overhead, that assumes that the client code is loaded in the ZEO process, and I thought one of the upcoming goals was to move conflict resolution to the client so as not to require the client code to be loaded in the ZEO process. Also, some common authorization schemes I've use (Pyramid's ACLs and zope.security) use not just an object in isolation, but the entire parent tree to make decisions, so they wouldn't be useful operating on just a single object/operation.

It also seems that authorization (and authentication too, come to think of it) would either have to disable the client-side persistent cache, or encrypt it based on a user-specific token issued by the ZEO server after authorization is complete.

Jason

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.