> From: [email protected] [mailto:[email protected]] On Behalf Of Ian Boston > > Hi Mike, > Thanks for the pointer. > > On 12 September 2013 14:58, Mike Müller <[email protected]> wrote: > > Hi > > > > The common way to solve such an access control for a provider like > > the Cassandra resource provider is the new ResourceAccessSecurity > > service. This is implemented in the bundle resourceaccesssecurity > > (at this time only read rights will be checked). > > Incidentally, how will other rights be enforced ? > the update pattern is resource.adaptTo(ModifiableValueMap.class) > > would the adapter factory check that the current user has write access > to the resource before they can get their hands on a > ModifiableValueMap ?
Yes, the resource will be wrapped to enforce the rights and the ModifiableValueMap as well... But as I said by now only read rights are enforced. The Cassandra resource provider is a very good example of a use case for this service. Best regards mike
