Attention aaa-devs, Autorelease sodium-mvn35-openjdk11 failed to build aaa-docs from aaa in build 157. Attached is a snippet of the error message related to the failure that we were able to

Attention aaa-devs, Autorelease sodium-mvn35-openjdk11 failed to build aaa-docs from aaa in build 156. Attached is a snippet of the error message related to the failure that we were able to

Hello, the minutes for this meeting are available at: Regards, Robert

Hello Robert We are still working with our customers on trying to determine the impact. The security team hasn’t been very responsive but we will try again and let you all know. Thanks -- Daniel

Hello Daniel, any update on the impact for your customers? Thanks, Robert

Hello, the minutes for this meeting are available at: Regards, Robert

Hello, the minutes for this meeting are available at: Sorry I have missed sending some of these out :( You can find the previous ones

Hi aaa devs, I just realized there is a typo in 3 RPC names

Hi, is it possible to define authorization policies on MD-SAL RPCs based on an input field? For example, I want to define policies on salflow service's 'add-flow' RPC which will restrict this RPC

OK.

Robert, thank you for the details. Abhijit, i think we still need to discuss the details during our next TSC meeting since it sounds like there will be major impact for our customers Thanks --

After Robert's explanation - do you still need it to be on the TSC agenda, Daniel (and maybe Luis)?

Sure.

Well, I am just a caretaker trying to get things moving forward. From what I remember, user credentials should not be affected, as that goes through Shiro, which is a separate thing. I would suspect

Hello Robert and all Our customers are also asking about the impact of this IdP removal with respect to their use of token authentication so @Abhijit Kumbhare can we add this topic to the next TSC

The web.xml mechanism was removed in Fluorine in lieu of instantiating the web app and securing it programmatically (via blueprint). For an example, check out

Hello everybody, Can somebody please tell me, how to secure our REST application with AAA? We have it done for Oxygen release, but it is not working for Fluorine SR1. What's more, documentation [0]

Hi Robert, Can you please explain the impact of this? e.g. can we for instance change the default user admin/admin or use token authentication after this change? BR/Luis

Hello everyone, as part of keeping OpenDaylight infrastructure secure and relevant, we will be removing OAuth2 Identity Provider component from the AAA project. There are three technical drivers

Great, thanks!