Robert, Thanks for your reply.
As you said, it is not possible with the current implementation and seems not possible in Helium as well, I am wondering that how such use case scenarios are being served with ODL. Scenario I have mentioned is a very practical one where my application (maintaining multiple users) wants to provide access only to that part of operational data which belongs to a user or you can say which should be accessible by user restricting access to other user's data. To All, please suggest if anyone has achieved any kind of solution to such problem. Thanks. Regards, Amit On Thu, Dec 22, 2016 at 3:34 PM, Robert Varga <n...@hq.sk> wrote: > On 12/22/2016 10:57 AM, Amit Kumar wrote: > > > > Use case I am interested in is that, user A should be authorized to > > access value (using RESTCONF) in "data" field only if list L's element > > is having "user" field set with value 'A' (i.e. username of user A) and > > similarly user B should be authorized to access value in "data" field > > only if list L's element is having "user" field set with value 'B'. > > > > Are there any ways to achieve such kind of controlled access, > > specifically in pre-karaf helium release? > > Addressing this requires an AAA-based overlay of DOMDataBroker. Not > currently available, and I am not sure if it is even doable on Helium > codebase. > > Regards, > Robert > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
