Hi Harshit, Did you replace the values in shiro.ini between square brackets <> with the appropriate values for your LDAP server? By the way, ODL Beryllium is very old and has not been supported for

For the sake of being open, this [0] is the partial AAA conversion patch, and [1] is needed to test RESTCONF (RESTCONF currently depends on AAA loading the jersey 1.17 runtime dependencies, which

Hi All, During the Kernel call this past Tuesday, we talked about attempting an isolated transition of AAA restful web services from Jersey 1 to Jersey 2. I attempted this change yesterday, and was

Yeah, I am all for implementing good practice by default too, and I understand this is not optimal. I purely wanted to make sure AAA didn't have a huge bug in the middle of it, which was my initial

Hi Ryan/Team, I am trying to onfigure OpenLdap with ODL (Beryllium version). I have done below changes in shiro.ini file ldapRealm =

Ryan & Stephen, this https://issues.apache.org/jira/browse/KARAF-5376?focusedCommentId=16431939&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16431939 may interest

it's up for interpretation as far as vulnerabilities. seems by default, the vulnerability is there. However, one can argue that users need to RTFM, go restart their deployment, ya da ya da ya da (hi

Cool, so there shouldn't be any gaping vulnerabilities as was originally indicated? Not sure what is installed for features by default anymore, but "jolokia" is part of the karaf standard features we

ok, yeah. after restarting, it seems the jolokia endpoint is now adhering to the proper credentials. I'm confused about the karaf jolokia stuff though. Is there no way to dump that and only allow our

Hello AAA devs, This is relevant to AAA... (I know Ryan intended to move away from Oltu, this just adds another nail to the coffin.) Regards, Stephen Begin forwarded message: Date: Sun, 8 Apr

Did you restart ODL after installing odl-jolikia? The issue is you have jolikia installed from karaf without auth, then try to install odl-jolikia which lays down org.jolikia.osgi.cfg with authMode

ok, I verified that carbon sr3 is working as we expect, but the recent Fluorine snapshot distro I have is not behaving like I expect. I am able to hit this

for carbon-sr3 we still hadn't integrated jolokia with AAA; it was still backed by etc/org.jolokia.osgi.cfg, hencewhy you need to use admin/admin after changing the password in AAA. How did you

I don't have access to my setup at the moment. I can later. but, I think it's based on carbon sr3. I do have a recent (2/27) snapshot distro from Fluorine though, and that actually doesn't even need

Jamo, can you comment on code version? Thanks! Regards, Ryan Goulding

Done. Apologies for the delay! Regards, Ryan Goulding

What version of code? This wasn’t tied to AAA until oxygen. Prior it was controlled by etc/or.jolokia.osgi.cfg. Thanks, Ryan

JamO, +aaa-dev and +controller-dev and Stephen FYI: This seems like a bug (bad one, security wise), but it's not for infrautils-dev - we don't actually do anything re. Jolokia in project infrautils,

Ryan, would you be able to do this?

Hi everyone, During the DDF we had a kernel projects planning session. Here are my notes: Fluorine kernel projects planning session Clustering ========== Improve clustering: look at the