[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread JIRA


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769009#comment-16769009
 ] 

Martin Krüger commented on KARAF-6153:
--

[~jbonofre]: I totally agree with your intentions to rather have a working 
product than avoid a hack which is required because of 3rd party limitiations. 
That is why I did not reopen the issue but was curious because I was not aware 
of this limitation. Thx for the quick answer and keep up the good work.

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (KARAF-6153) Instance fails to start

2019-02-14 Thread JIRA


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769005#comment-16769005
 ] 

Jean-Baptiste Onofré edited comment on KARAF-6153 at 2/15/19 6:51 AM:
--

[~martin.krueger] due to a limitation in the resource plugin, we can't have two 
executions as the delimiter can't be located in the execution configuration 
section (it has to be global configuration). That's a quick fix anyway (I 
prefer to have instances working than the warning). I will find a better way.


was (Author: jbonofre):
[~martin.krueger] due to a limitation in the resource plugin, we can't have two 
execution as the delimiter can't be located in the execution section (it has to 
be global configuration). That's a quick fix anyway (I prefer to have instances 
working than the warning). I will find a better way.

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread JIRA


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769005#comment-16769005
 ] 

Jean-Baptiste Onofré commented on KARAF-6153:
-

[~martin.krueger] due to a limitation in the resource plugin, we can't have two 
execution as the delimiter can't be located in the execution section (it has to 
be global configuration). That's a quick fix anyway (I prefer to have instances 
working than the warning). I will find a better way.

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread JIRA


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768999#comment-16768999
 ] 

Martin Krüger commented on KARAF-6153:
--

[~jbonofre]: Is this the intended final solution? When I compile the instance 
module now I get a big warning.

{noformat}
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.karaf.instance:org.apache.karaf.instance.core:bundle:4.3.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found 
duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin 
@ org.apache.karaf.instance:org.apache.karaf.instance.core:[unknown-version], 
/home/user1/gitKaraf/instance/pom.xml, line 177, column 21
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
{noformat}

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KARAF-6146) Decanter log alerter throws a NullPointerException

2019-02-14 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KARAF-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-6146:

Summary: Decanter log alerter throws a NullPointerException  (was: Decanter 
log alerter throws a NuullPointerException)

> Decanter log alerter throws a NullPointerException
> --
>
> Key: KARAF-6146
> URL: https://issues.apache.org/jira/browse/KARAF-6146
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-2.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: decanter-2.2.0
>
>
> When using the Decanter log alerter (mainly for demo or test), it throws a 
> {{NullPointerException}} when an alert is displayed:
> {code}
> 07:42:00.641 WARN [EventAdminAsyncThread #7] EventAdmin: Exception during 
> event dispatch [org.osgi.service.event.Event [topic=decanter/alert/warn] 
> {hostName=precision, alertPattern=range:[0,10), 
> felix.fileinstall.filename=file:/home/jbonofre/Downloads/apache-karaf-4.2.1/etc/org.apache.karaf.decanter.collector.jmx-local.cfg,
>  CurrentThreadCpuTimeSupported=true, CurrentThreadUserTime=1000, 
> PeakThreadCount=133, type=jmx-local, 
> service.factoryPid=org.apache.karaf.decanter.collector.jmx, 
> decanter.collector.name=jmx, scheduler.period=60, 
> ThreadCpuTimeSupported=true, scheduler.concurrent=false, component.id=10, 
> karafName=root, host=null, scheduler.name=decanter-collector-jmx, 
> alertAttribute=ThreadCount, DaemonThreadCount=57, timestamp=1549694520576, 
> ThreadAllocatedMemorySupported=true, ThreadContentionMonitoringEnabled=false, 
> component.name=org.apache.karaf.decanter.collector.jmx, 
> TotalStartedThreadCount=208, alertLevel=warn, AllThreadIds=[J@bb4618e, 
> ThreadAllocatedMemoryEnabled=true, CurrentThreadCpuTime=25464364, url=local, 
> ObjectName=java.lang:type=Threading, 
> service.pid=org.apache.karaf.decanter.collector.jmx.fc1deb09-fca8-4d94-a0ab-456a0cab62d2,
>  ThreadContentionMonitoringSupported=true, ThreadCount=105, 
> alertBackToNormal=false, ThreadCpuTimeEnabled=true, 
> ObjectMonitorUsageSupported=true, hostAddress=127.0.0.1, 
> SynchronizerUsageSupported=true} | [org.osgi.service.event.EventHandler] | 
> Bundle(org.apache.karaf.decanter.alerting.log [94])]
> java.lang.NullPointerException: null
> at 
> org.apache.karaf.decanter.alerting.log.Logger.handleEvent(Logger.java:38) 
> ~[?:?]
> at 
> org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> org.apache.felix.eventadmin.impl.tasks.HandlerTask.runWithoutBlacklistTiming(HandlerTask.java:82)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:104)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:166)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [?:?]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [?:?]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (KARAF-6146) Decanter log alerter throws a NullPointerException

2019-02-14 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KARAF-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-6146.
-
Resolution: Fixed

> Decanter log alerter throws a NullPointerException
> --
>
> Key: KARAF-6146
> URL: https://issues.apache.org/jira/browse/KARAF-6146
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-2.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: decanter-2.2.0
>
>
> When using the Decanter log alerter (mainly for demo or test), it throws a 
> {{NullPointerException}} when an alert is displayed:
> {code}
> 07:42:00.641 WARN [EventAdminAsyncThread #7] EventAdmin: Exception during 
> event dispatch [org.osgi.service.event.Event [topic=decanter/alert/warn] 
> {hostName=precision, alertPattern=range:[0,10), 
> felix.fileinstall.filename=file:/home/jbonofre/Downloads/apache-karaf-4.2.1/etc/org.apache.karaf.decanter.collector.jmx-local.cfg,
>  CurrentThreadCpuTimeSupported=true, CurrentThreadUserTime=1000, 
> PeakThreadCount=133, type=jmx-local, 
> service.factoryPid=org.apache.karaf.decanter.collector.jmx, 
> decanter.collector.name=jmx, scheduler.period=60, 
> ThreadCpuTimeSupported=true, scheduler.concurrent=false, component.id=10, 
> karafName=root, host=null, scheduler.name=decanter-collector-jmx, 
> alertAttribute=ThreadCount, DaemonThreadCount=57, timestamp=1549694520576, 
> ThreadAllocatedMemorySupported=true, ThreadContentionMonitoringEnabled=false, 
> component.name=org.apache.karaf.decanter.collector.jmx, 
> TotalStartedThreadCount=208, alertLevel=warn, AllThreadIds=[J@bb4618e, 
> ThreadAllocatedMemoryEnabled=true, CurrentThreadCpuTime=25464364, url=local, 
> ObjectName=java.lang:type=Threading, 
> service.pid=org.apache.karaf.decanter.collector.jmx.fc1deb09-fca8-4d94-a0ab-456a0cab62d2,
>  ThreadContentionMonitoringSupported=true, ThreadCount=105, 
> alertBackToNormal=false, ThreadCpuTimeEnabled=true, 
> ObjectMonitorUsageSupported=true, hostAddress=127.0.0.1, 
> SynchronizerUsageSupported=true} | [org.osgi.service.event.EventHandler] | 
> Bundle(org.apache.karaf.decanter.alerting.log [94])]
> java.lang.NullPointerException: null
> at 
> org.apache.karaf.decanter.alerting.log.Logger.handleEvent(Logger.java:38) 
> ~[?:?]
> at 
> org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> org.apache.felix.eventadmin.impl.tasks.HandlerTask.runWithoutBlacklistTiming(HandlerTask.java:82)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:104)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:166)
>  [3:org.apache.karaf.services.eventadmin:4.2.1]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [?:?]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [?:?]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (KARAF-6158) SecurityContext returns RolePrincipal instead of UserPrincipal in JAX-RS

2019-02-14 Thread Matt Pavlovich (JIRA)
Matt Pavlovich created KARAF-6158:
-

 Summary: SecurityContext returns RolePrincipal instead of 
UserPrincipal in JAX-RS
 Key: KARAF-6158
 URL: https://issues.apache.org/jira/browse/KARAF-6158
 Project: Karaf
  Issue Type: Bug
Affects Versions: 4.1.5
Reporter: Matt Pavlovich


The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
RolePrincipal instead of UserPrincipal. 

* Custom JAAS provider
* Only one JAAS provider
* Realm named 'karaf'

Seems like same issue posted to karaf-users mailinglist [Nabble 
link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KARAF-6156) Support extending Karaf JAAS Principal classes

2019-02-14 Thread Matt Pavlovich (JIRA)


 [ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Pavlovich updated KARAF-6156:
--
Description: 
JAASHelper prevents extension of Karaf's JAAS Principal classes [User, 
Group,Role]Principal by doing a class.getName().equals(..). This change 
replaces it with a class.isAssignableFrom( .. ) comparison to allow for JAAS 
providers to extend the Karaf Principal classes.

Supporting this provides extended feature, and provides a work-around for 
mis-behaving JAAS and SecurityContext implementations. 

Specifically, as observed in KARAF-6158

  was:JAASHelper prevents extension of Karaf's JAAS Principal classes [User, 
Group,Role]Principal by doing a class.getName().equals(..). This change 
replaces it with a class.isAssignableFrom( .. ) comparison to allow for JAAS 
providers to extend the Karaf Principal classes


> Support extending Karaf JAAS Principal classes
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> JAASHelper prevents extension of Karaf's JAAS Principal classes [User, 
> Group,Role]Principal by doing a class.getName().equals(..). This change 
> replaces it with a class.isAssignableFrom( .. ) comparison to allow for JAAS 
> providers to extend the Karaf Principal classes.
> Supporting this provides extended feature, and provides a work-around for 
> mis-behaving JAAS and SecurityContext implementations. 
> Specifically, as observed in KARAF-6158



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768439#comment-16768439
 ] 

ASF subversion and git services commented on KARAF-6153:


Commit a408cdcd04b67b0545cff913012f5b3343090a0c in karaf's branch 
refs/heads/karaf-4.2.x from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=a408cdc ]

[KARAF-6153] Fix the instance resources filtering and add new instance itest


> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (KARAF-6153) Instance fails to start

2019-02-14 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-6153.
-
Resolution: Fixed

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KARAF-6156) Support extending Karaf JAAS Principal classes

2019-02-14 Thread Matt Pavlovich (JIRA)


 [ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Pavlovich updated KARAF-6156:
--
Description: JAASHelper prevents extension of Karaf's JAAS Principal 
classes [User, Group,Role]Principal by doing a class.getName().equals(..). This 
change replaces it with a class.isAssignableFrom( .. ) comparison to allow for 
JAAS providers to extend the Karaf Principal classes  (was: The SecurityContext 
in a CXFJAX-RS service is ~75% of the time returning a RolePrincipal instead of 
UserPrincipal. 

* Custom JAAS provider
* Only one JAAS provider
* Realm named 'karaf'

Seems like same issue posted to karaf-users mailinglist [Nabble 
link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html])

> Support extending Karaf JAAS Principal classes
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> JAASHelper prevents extension of Karaf's JAAS Principal classes [User, 
> Group,Role]Principal by doing a class.getName().equals(..). This change 
> replaces it with a class.isAssignableFrom( .. ) comparison to allow for JAAS 
> providers to extend the Karaf Principal classes



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KARAF-6156) Support extending Karaf JAAS Principal classes

2019-02-14 Thread Matt Pavlovich (JIRA)


 [ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Pavlovich updated KARAF-6156:
--
Summary: Support extending Karaf JAAS Principal classes  (was: Support 
extending Karaf JAAS Principals)

> Support extending Karaf JAAS Principal classes
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KARAF-6156) Support extending Karaf JAAS Principals

2019-02-14 Thread Matt Pavlovich (JIRA)


 [ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Pavlovich updated KARAF-6156:
--
Summary: Support extending Karaf JAAS Principals  (was: SecurityContext 
returns RolePrincipal instead of UserPrincipal)

> Support extending Karaf JAAS Principals
> ---
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768431#comment-16768431
 ] 

ASF subversion and git services commented on KARAF-6153:


Commit 9f3a6a4293bb3ff94c1fd3296bed807975f0fef8 in karaf's branch 
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=9f3a6a4 ]

[KARAF-6153] Fix the instance resources filtering and add new instance itest


> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768429#comment-16768429
 ] 

ASF GitHub Bot commented on KARAF-6153:
---

jbonofre commented on pull request #768: [KARAF-6153] Fix the instance 
resources filtering and add new instance itest
URL: https://github.com/apache/karaf/pull/768
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768433#comment-16768433
 ] 

ASF subversion and git services commented on KARAF-6153:


Commit 0952a6eb743603a7438461a3289106cd2c3944c9 in karaf's branch 
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=0952a6e ]

Merge pull request #768 from jbonofre/KARAF-6153

[KARAF-6153] Fix the instance resources filtering and add new instance itest

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768432#comment-16768432
 ] 

ASF subversion and git services commented on KARAF-6153:


Commit 0952a6eb743603a7438461a3289106cd2c3944c9 in karaf's branch 
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=0952a6e ]

Merge pull request #768 from jbonofre/KARAF-6153

[KARAF-6153] Fix the instance resources filtering and add new instance itest

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768318#comment-16768318
 ] 

ASF GitHub Bot commented on KARAF-6156:
---

jbonofre commented on pull request #765: [KARAF-6156] Update JaasHelper to 
support extending Karaf JAAS (4.1.x)
URL: https://github.com/apache/karaf/pull/765
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-6156.
-
Resolution: Fixed

> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768317#comment-16768317
 ] 

ASF subversion and git services commented on KARAF-6156:


Commit 71c881d39ff9b8ec7691df3092888d318036b2b7 in karaf's branch 
refs/heads/karaf-4.1.x from Matt Pavlovich
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=71c881d ]

[KARAF-6156] Update to support extending Karaf JAAS [User,Group,Role]Principal 
classes


> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768314#comment-16768314
 ] 

ASF subversion and git services commented on KARAF-6156:


Commit b0f3a5ffeb1101be1e4b06695ebaaebc56effd54 in karaf's branch 
refs/heads/karaf-4.2.x from Matt Pavlovich
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=b0f3a5f ]

[KARAF-6156] Update to support extending Karaf JAAS [User,Group,Role]Principal 
classes


> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768309#comment-16768309
 ] 

ASF subversion and git services commented on KARAF-6156:


Commit ef93cd77cf18d085eff72d5d26ff474c7e3e330f in karaf's branch 
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=ef93cd7 ]

Merge pull request #766 from mattrpav/KARAF-6156-43x

[KARAF-6156] Update JaasHelper to support extending Karaf JAAS (4.3.x)

> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768308#comment-16768308
 ] 

ASF subversion and git services commented on KARAF-6156:


Commit c03fa2f228852d805d1201c3a9f2b3c4abcb2a60 in karaf's branch 
refs/heads/master from Matt Pavlovich
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=c03fa2f ]

[KARAF-6156] Update to support extending Karaf JAAS [User,Group,Role]Principal 
classes


> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768311#comment-16768311
 ] 

ASF GitHub Bot commented on KARAF-6156:
---

jbonofre commented on pull request #766: [KARAF-6156] Update JaasHelper to 
support extending Karaf JAAS (4.3.x)
URL: https://github.com/apache/karaf/pull/766
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6156) SecurityContext returns RolePrincipal instead of UserPrincipal

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768310#comment-16768310
 ] 

ASF subversion and git services commented on KARAF-6156:


Commit ef93cd77cf18d085eff72d5d26ff474c7e3e330f in karaf's branch 
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=ef93cd7 ]

Merge pull request #766 from mattrpav/KARAF-6156-43x

[KARAF-6156] Update JaasHelper to support extending Karaf JAAS (4.3.x)

> SecurityContext returns RolePrincipal instead of UserPrincipal
> --
>
> Key: KARAF-6156
> URL: https://issues.apache.org/jira/browse/KARAF-6156
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.1.6
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
>
> The SecurityContext in a CXFJAX-RS service is ~75% of the time returning a 
> RolePrincipal instead of UserPrincipal. 
> * Custom JAAS provider
> * Only one JAAS provider
> * Realm named 'karaf'
> Seems like same issue posted to karaf-users mailinglist [Nabble 
> link|http://karaf.922171.n3.nabble.com/securityContext-getUserPrincipal-in-JAX-RS-return-unexpected-RolePrincipal-Why-tt4053628.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KARAF-6153) Instance fails to start

2019-02-14 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-6153:

Fix Version/s: (was: 4.1.8)

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KARAF-6153) Instance fails to start

2019-02-14 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-6153:

Fix Version/s: 4.1.8

> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.1.8, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6153) Instance fails to start

2019-02-14 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768267#comment-16768267
 ] 

ASF GitHub Bot commented on KARAF-6153:
---

jbonofre commented on pull request #768: [KARAF-6153] Fix the instance 
resources filtering and add new instance itest
URL: https://github.com/apache/karaf/pull/768
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Instance fails to start
> ---
>
> Key: KARAF-6153
> URL: https://issues.apache.org/jira/browse/KARAF-6153
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 4.2.2, 4.2.3
>Reporter: Akhil Grover
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
> Attachments: karaf.log
>
>
> Karaf creates a new instance but the instance does not start.
> {code}
> karaf@root()> instance:create test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()> instance:start test
> karaf@root()> instance:list
> SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI 
> Server Host | State | PID | Name
> -+--+--+---++-+-+---+-
>  8101 | 0.0.0.0 | 1099 | 127.0.0.1 | 4 | 127.0.0.1 | Started | 28644 | 
> root
>  8102 | 0.0.0.0 | 1100 | 127.0.0.1 | 5 | 127.0.0.1 | Stopped | 0 | test
> karaf@root()>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles

2019-02-14 Thread Freeman Fang (JIRA)


 [ 
https://issues.apache.org/jira/browse/KARAF-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved KARAF-6157.
-
   Resolution: Fixed
Fix Version/s: 4.2.4
   4.3.0

> ensure karaf-maven-plugin can honor start-level for bootBundles
> ---
>
> Key: KARAF-6157
> URL: https://issues.apache.org/jira/browse/KARAF-6157
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
>
> the bundle element in generated features.xml should have start-level 
> configured accordingly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768002#comment-16768002
 ] 

ASF subversion and git services commented on KARAF-6157:


Commit b531a0dac6b85e7f559979db5d5b975d319462b4 in karaf's branch 
refs/heads/master from Freeman Fang
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=b531a0d ]

[KARAF-6157]ensure karaf-maven-plugin can honor start-level for bootBundles


> ensure karaf-maven-plugin can honor start-level for bootBundles
> ---
>
> Key: KARAF-6157
> URL: https://issues.apache.org/jira/browse/KARAF-6157
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> the bundle element in generated features.xml should have start-level 
> configured accordingly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles

2019-02-14 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/KARAF-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768003#comment-16768003
 ] 

ASF subversion and git services commented on KARAF-6157:


Commit 58eae75a40061e3ffb1606e5b0ac2c0b0b65346a in karaf's branch 
refs/heads/karaf-4.2.x from Freeman Fang
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=58eae75 ]

[KARAF-6157]ensure karaf-maven-plugin can honor start-level for bootBundles

(cherry picked from commit b531a0dac6b85e7f559979db5d5b975d319462b4)


> ensure karaf-maven-plugin can honor start-level for bootBundles
> ---
>
> Key: KARAF-6157
> URL: https://issues.apache.org/jira/browse/KARAF-6157
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 4.3.0, 4.2.4
>
>
> the bundle element in generated features.xml should have start-level 
> configured accordingly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles

2019-02-14 Thread Freeman Fang (JIRA)


 [ 
https://issues.apache.org/jira/browse/KARAF-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang reassigned KARAF-6157:
---

Assignee: Freeman Fang

> ensure karaf-maven-plugin can honor start-level for bootBundles
> ---
>
> Key: KARAF-6157
> URL: https://issues.apache.org/jira/browse/KARAF-6157
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> the bundle element in generated features.xml should have start-level 
> configured accordingly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (KARAF-6157) ensure karaf-maven-plugin can honor start-level for bootBundles

2019-02-14 Thread Freeman Fang (JIRA)
Freeman Fang created KARAF-6157:
---

 Summary: ensure karaf-maven-plugin can honor start-level for 
bootBundles
 Key: KARAF-6157
 URL: https://issues.apache.org/jira/browse/KARAF-6157
 Project: Karaf
  Issue Type: Improvement
Reporter: Freeman Fang


the bundle element in generated features.xml should have start-level configured 
accordingly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)