We occasionally have AAA tech meetings at 9PST on Tuesdays… Guess that conflicts with MD-SAL meeting :\. I will move this topic for this Thursday then… and we need a new date/time for tech

What time today? The MD-SAL meeting is at 9am PST... I'd be happy to help in intro-ing the MD-SAL to the AAA team though :) Ed From: aaa-dev-bounces@... [aaa-dev-bounces@...] on behalf of Nguyen,

Hi guys, I don’t see a meeting for AAA on my calendar today… Are we having a tech meeting? I think from last time, the agenda is going to include intro to MD-SAL and a presentation of

First, apologies for the major email blast, but pretty much everybody gets covered by this one... Second, apologies if I missed any projects that declared intent to be part of helium - I'm not 100%

My laptop is down and I cannot get WebEx to work correctly on my Ubuntu box…. Let’s meet via #opendaylight-aaa today… sorry, guys. Liem

Hi John, I don't suggest hard-coding mapping logics... It should be some sort of JSON mapping file; there just won't be any API for it, unless someone has the bandwidth. For user/role assignment, we

On 06/16/2014 07:49 PM, Nguyen, Liem Manh wrote: Hmm... for some reason my email client (Thunderbird) is having trouble quoting your message in my reply (your text is a single long line

Hi John, My response in-line below… Cheers, Liem

Hi Liem: Thank you for sending out the sequence diagrams, they've been very helpful. Also thank you for posting the code to a public git repo. The code looks clean, nicely organized and

We are using MD-SAL APIs for dlux. In your release plan there is still a question mark on that, as we know MD-SAL does not have any authentication. Once you update your plan for MD-SAL API’s

Hi everyone, For Helium, AAA plans to deliver token-based authentication (vs what we do today which is HTTP basic). An example of that is documented in the “Running” section of the

I think that would call for a set of implementation which will talk to the ThreadLocal context, e.g. ExecutorService.submit() would look at the store and attach the current context to the work being

I missed that meeting and thus don't have context, but my first question is why do you need to do this at all? That is, in my world-view, the incoming northbound request is steered to the appropriate

Guys, At the AAA meeting this week, as Liem was walking us through the code, he showed us attaching security context to an InheritableThreadLocal store (meaning, its context is the thread or its

When: Tuesday, June 17, 2014 6:00 PM-7:00 PM. (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna *~*~*~*~*~*~*~*~*~* Additional call… Likely agenda: Continue current code discussion /

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

Sorry for spamming if you got this twice… There was a hiccup with the mailing list. Hi guys, I updated the Wiki page to include some potential integration areas with other projects:

Hi guys, I updated the Wiki page to include some potential integration areas with other projects: https://wiki.opendaylight.org/view/AAA:Helium#Expected_Dependencies_on_Other_Projects

more details » OpenDaylight New Project Startup Help The goal of this meeting is to help projects that are new to OpenDaylight setup and begin to use their infrastructure

Thanks Liem, and you are very welcome. Phil.