Hi Ryan, I'll look at it on Monday. AFAIK there are no special ACLs for the instance commands (at least not by default). So you might have possibly found a bug...
Cheers, David On 20 December 2013 21:47, Ryan Moquin <fragility...@gmail.com> wrote: > Hi, I ran into a problem recently as I was working on some code where Karaf > responds with the following error when I execute an "instance:stop" command: > > Caused by: java.lang.SecurityException: Insufficient credentials. > at > org.apache.karaf.service.guard.impl.GuardProxyCatalog$ProxyInvocationListener.preInvoke(GuardProxyCatalog.java:527)[27:org.apache.karaf.ser > vice.guard:3.0.0.SNAPSHOT] > at > org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:52)[12:org.apache.aries.proxy.impl:1.0.2] > at > org.apache.aries.proxy.impl.ProxyHandler.invoke(ProxyHandler.java:119)[12:org.apache.aries.proxy.impl:1.0.2] > at > org.apache.karaf.shell.console.commands.$BlueprintCommand1284042692.execute(Unknown > Source)[39:org.apache.karaf.shell.console:3.0.0.SNAPSHO > T] > at > org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78) > ... > > I'm using the default karaf/karaf credentials which work to connect to an > instance, but for some reason this happens whenever I try to stop the > instance... is there something additional to be aware of in regards to the > GuardProxyCatalog? I'm going to take a look at the source, but just in case > nothing turns up, I thought I'd ask to see if anyone has ran into something > like this? > > Regards, > Ryan
