I think it's perfectly reasonable to allow for granular control of restconf behavior via meta-data (ie extensions) in the yang model. At my last company, we had similar use cases and functionality in

I do not want to disable REST, I want to selectively disallow REST for certain containers, models. Making some of them operational as Rob suggested can solve some but not all. An yang extension would

Hi Reinaldo, Yes, we plan to have RBAC over MD-SAL…. This is work in progress and not there in the code yet. For now, I think you can simply disable the sal-rest-connector bundle if you don’t

The AAA project is planning to deliver access control on top of the MD-SAL, and they have the current status listed as PoC on their release page: https://wiki.opendaylight.org/view/AAA:Helium I'm

Hi Liem, after updating my repo to the latest, I noticed that the authentication "curl" instructions no longer work, and I cannot get past the auth stage. Looking at the code the new IdMService now

Hi Wojciech, I don’t really see a use-case for exposing AuthZ via REST… In fact, I think it might be a security issue, since it exposes too much of the inner workings of the AAA system for a

Hi All, given that this is an initial model, I'm collecting your feedback on, and mindful of the fact that Yang syntax might be new to some, here's some additional description. The Yang model consists

Hi Folks, while working through the config sub-system wiring, I came to a question that calls for some wider input. As far as I understand, there are two types of wiring API ends that can be used a)

Hi Folks, here's the initial authorization model, that I would like to propose for starters. Key inputs exected to be provided by the AuthN sub-system are: role and domain-name. The idea is that the

FYI... Some minor refactoring so we are consistent in terms of naming (no more "tenant"). This has been pushed into master. Cheers, Liem

Looks like it's working now... Liem

Yep, same issue here... Wojciech needs to change it, since I am not the host. Liem

The meeting was moved up 1/2 hour but the webex link in the meeting invite still thinks the meeting is at the original time and is not allowing me to connect early. -- John

Hi guys, Proposed agenda (in addition to status) for tomorrow: Update on MD-SAL AuthZ design/progress I added a decorator for BlockingQueue to help with auth context transfer across thread

Just sent out an updated invite...

When: Thursday, June 26, 2014 5:30 PM-6:30 PM. (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna*~*~*~*~*~*~*~*~*~* Agenda: Status (https://trello.com/b/ehBCSGY3/opendaylight-aaa) What was

On 06/24/2014 11:34 AM, Nguyen, Liem Manh wrote: Ok for me -- John

On 06/24/2014 11:31 AM, Nguyen, Liem Manh wrote: works for me -- John

I would be :) Ed

Hi guys, My kid’s summer camp schedule throws me for a loop, and I need to move the AAA status meetings on Thursdays 1/2 hour early (8:30AM PST instead of 9AM), at least for the next couple of