Re: JAAS in Karaf4/5

2021-05-19 Thread Bernd
Hello, Am Mi., 19. Mai 2021 um 11:38 Uhr schrieb Jean-Baptiste Onofre < j...@nanthrax.net>: > Karaf5 service could be a nice location, but keep in mind that Karaf5 > service are not OSGi service (the osgi application manager is itself a K5 > service). > I guess for normal client code it doesnt

Re: JAAS in Karaf4/5

2021-05-19 Thread Romain Manni-Bucau
Hi Le mer. 19 mai 2021 à 11:31, Bernd a écrit : > Hello, > > I noticed that Karaf provides quite useful principals for Roles, Groups and > Client. But if I want to consume or create those principals in my own code, > I have to depend on the karaf-boot bundle. > > I wonder: > > a) would it

Re: JAAS in Karaf4/5

2021-05-19 Thread Jean-Baptiste Onofre
Hi Bernd, Thanks for your feedback and proposal. Generally speaking I agree with the proposal. Karaf5 service could be a nice location, but keep in mind that Karaf5 service are not OSGi service (the osgi application manager is itself a K5 service). So, I think we can already prepare some

JAAS in Karaf4/5

2021-05-19 Thread Bernd
Hello, I noticed that Karaf provides quite useful principals for Roles, Groups and Client. But if I want to consume or create those principals in my own code, I have to depend on the karaf-boot bundle. I wonder: a) would it make sense for Karaf5 to move the classes to a more focused API jar.

Re: [PROPOSAL] Disable autoRefresh on features service by default and simple optional features service

2021-05-19 Thread Jean-Baptiste Onofre
Same for me ;) So, let me refactor and remove "my" feature.simple bundle to include in features.core. I will create the PR soon. Regards JB > Le 19 mai 2021 à 09:21, Grzegorz Grzybek a écrit : > > śr., 19 maj 2021 o 08:59 Jean-Baptiste Onofre napisał(a): > >> Yes, both are possible. >>

Re: [PROPOSAL] Disable autoRefresh on features service by default and simple optional features service

2021-05-19 Thread Grzegorz Grzybek
śr., 19 maj 2021 o 08:59 Jean-Baptiste Onofre napisał(a): > Yes, both are possible. > > Maybe keeping all in org.apache.karaf.features.core with a configuration > to use a different deploy/approach is better than a complete new features > bundle. > It’s not a problem to me to refactor what I

Re: [PROPOSAL] Disable autoRefresh on features service by default and simple optional features service

2021-05-19 Thread Jean-Baptiste Onofre
Yes, both are possible. Maybe keeping all in org.apache.karaf.features.core with a configuration to use a different deploy/approach is better than a complete new features bundle. It’s not a problem to me to refactor what I did. Thoughts ? Regards JB > Le 19 mai 2021 à 08:01, Grzegorz Grzybek

Re: [PROPOSAL] Disable autoRefresh on features service by default and simple optional features service

2021-05-19 Thread Grzegorz Grzybek
śr., 19 maj 2021 o 07:53 Jean-Baptiste Onofre napisał(a): > Hi, > > Actually, it’s a complete separated bundle. > > So, in the Karaf standard distribution, you will have > org.apache.karaf.features.core in etc/startup.properties: that’s the > regular/current one with the resolver. > >