December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2100) Upgrade to WildFly Elytron 1.1.0.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2100: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Final Key: WFCORE-2100 URL: https://issues.jboss.org/browse/WFCORE-2100 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7041) Add testing for Web -> EJB Identity Propagation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7041?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7041: ---------------------------------------- [~honza889] This would be within the WildFly testsuite but using configuration backed by the Elytron subsystem. The subsystem itself does not have (and should not have) the containers running. > Add testing for Web -> EJB Identity Propagation > ----------------------------------------------- > > Key: WFLY-7041 > URL: https://issues.jboss.org/browse/WFLY-7041 > Project: WildFly > Issue Type: Task > Components: EJB, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Labels: elytron_testing > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7041) Add testing for Web -> EJB Identity Propagation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7041?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-7041 at 12/9/16 5:24 AM: ----------------------------------------------------------- This will be part of tests in *wildfly* repository. Does this issue mean this test should be part of *elytron-subsystem* too? was (Author: honza889): This will be part of Common criteria tests in *wildfly* repository. Does this issue mean this test should be part of *elytron-subsystem* too? > Add testing for Web -> EJB Identity Propagation > ----------------------------------------------- > > Key: WFLY-7041 > URL: https://issues.jboss.org/browse/WFLY-7041 > Project: WildFly > Issue Type: Task > Components: EJB, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Labels: elytron_testing > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7041) Add testing for Web -> EJB Identity Propagation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7041?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7041: ---------------------------------- This will be part of Common criteria tests in *wildfly* repository. Does this issue mean this test should be part of *elytron-subsystem* too? > Add testing for Web -> EJB Identity Propagation > ----------------------------------------------- > > Key: WFLY-7041 > URL: https://issues.jboss.org/browse/WFLY-7041 > Project: WildFly > Issue Type: Task > Components: EJB, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Labels: elytron_testing > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1378) Option: Force reading String from a Numeric type cell in SpreadSheet

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1378?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-1378: -------------------------------------- Git Pull Request: https://github.com/droolsjbpm/drools/pull/1030 > Option: Force reading String from a Numeric type cell in SpreadSheet > -------------------------------------------------------------------- > > Key: DROOLS-1378 > URL: https://issues.jboss.org/browse/DROOLS-1378 > Project: Drools > Issue Type: Feature Request > Components: decision tables > Affects Versions: 7.0.0.Beta4 > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > > org.drools.decisiontable.parser.xls.ExcelParser reads a double value from a Numeric type cell. But some users expect as-is String representation rather than a double value. Users may force String type by adding heading ' (apostrophe) in the cell but sometimes it could be cumbersome. > This JIRA requests an option to force reading String from a Numeric type cell in SpreadSheet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1378) Option: Force reading String from a Numeric type cell in SpreadSheet

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created DROOLS-1378: ----------------------------------------- Summary: Option: Force reading String from a Numeric type cell in SpreadSheet Key: DROOLS-1378 URL: https://issues.jboss.org/browse/DROOLS-1378 Project: Drools Issue Type: Feature Request Components: decision tables Affects Versions: 7.0.0.Beta4 Reporter: Toshiya Kobayashi Assignee: Mario Fusco org.drools.decisiontable.parser.xls.ExcelParser reads a double value from a Numeric type cell. But some users expect as-is String representation rather than a double value. Users may force String type by adding heading ' (apostrophe) in the cell but sometimes it could be cumbersome. This JIRA requests an option to force reading String from a Numeric type cell in SpreadSheet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-864) NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug... ] Philippe Marschall commented on SECURITY-864: --------------------------------------------- [~mletenay] we went with a custom [JNDI ObjectFactory|https://github.com/marschall/policy-registration-factory], that keeps our LoginModule clean from work arounds and solves the issue we had with read only JNDI. > NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration > ------------------------------------------------------------------------------------------------------- > > Key: SECURITY-864 > URL: https://issues.jboss.org/browse/SECURITY-864 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Reporter: Chao Wang > Assignee: Stefan Guilhen > > "NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration" is recorded in server.log during quickstart example run by changing log level: > {noformat} > <logger category="org.jboss.as.security"> > <level name="TRACE"/> > </logger> > <logger category="org.jboss.security"> > <level name="TRACE"/> > </logger> > {noformat} > See detailed description in community discussion [#907134|https://developer.jboss.org/message/907134] > I choose Jira component picketbox since the exception is titled as "PBOX000293: Exception caught: javax.naming.NameNotFoundException" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7772) Distributed cache is created in REPLICATED mode

by Richard Janík (JIRA)

Richard Janík created WFLY-7772: ----------------------------------- Summary: Distributed cache is created in REPLICATED mode Key: WFLY-7772 URL: https://issues.jboss.org/browse/WFLY-7772 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Richard Janík Assignee: Paul Ferraro While trying to verify a different issue, I configured a {{<distributed-cache>}} with {{l1-lifespan=300000}} and added a Clusterbench deployment. The EAP start failed with: {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache-configuration.web.routing: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache-configuration.web.routing: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1919) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000350: Enabling the L1 cache is only supported when using DISTRIBUTED as a cache mode. Your cache mode is set to REPLICATED at org.infinispan.configuration.cache.L1ConfigurationBuilder.validate(L1ConfigurationBuilder.java:97) at org.infinispan.configuration.cache.ClusteringConfigurationBuilder.validate(ClusteringConfigurationBuilder.java:108) at org.infinispan.configuration.cache.ConfigurationBuilder.validate(ConfigurationBuilder.java:203) at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:246) at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:236) at org.wildfly.clustering.infinispan.spi.service.ConfigurationBuilder.start(ConfigurationBuilder.java:88) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) ... 3 more {code} The full config is here: http://pastebin.test.redhat.com/437800 The cache has {{owners=1}}, but that does not matter, the exception is thrown with the default {{owners=2}} as well. And the full server log is here: http://pastebin.test.redhat.com/437799 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7772) Distributed cache is created in REPLICATED mode

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-7772?page=com.atlassian.jira.plugin.... ] Richard Janík updated WFLY-7772: -------------------------------- Affects Version/s: 10.1.0.Final > Distributed cache is created in REPLICATED mode > ----------------------------------------------- > > Key: WFLY-7772 > URL: https://issues.jboss.org/browse/WFLY-7772 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Richard Janík > Assignee: Paul Ferraro > > While trying to verify a different issue, I configured a {{<distributed-cache>}} with {{l1-lifespan=300000}} and added a Clusterbench deployment. The EAP start failed with: > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache-configuration.web.routing: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache-configuration.web.routing: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1919) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000350: Enabling the L1 cache is only supported when using DISTRIBUTED as a cache mode. Your cache mode is set to REPLICATED > at org.infinispan.configuration.cache.L1ConfigurationBuilder.validate(L1ConfigurationBuilder.java:97) > at org.infinispan.configuration.cache.ClusteringConfigurationBuilder.validate(ClusteringConfigurationBuilder.java:108) > at org.infinispan.configuration.cache.ConfigurationBuilder.validate(ConfigurationBuilder.java:203) > at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:246) > at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:236) > at org.wildfly.clustering.infinispan.spi.service.ConfigurationBuilder.start(ConfigurationBuilder.java:88) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > ... 3 more > {code} > The full config is here: > http://pastebin.test.redhat.com/437800 > The cache has {{owners=1}}, but that does not matter, the exception is thrown with the default {{owners=2}} as well. > And the full server log is here: > http://pastebin.test.redhat.com/437799 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7771) Failed to obtain ApplicationPolicy for domain other

by Albert Borgen (JIRA)

[ https://issues.jboss.org/browse/WFLY-7771?page=com.atlassian.jira.plugin.... ] Albert Borgen commented on WFLY-7771: ------------------------------------- Yes. Right. > Failed to obtain ApplicationPolicy for domain other > --------------------------------------------------- > > Key: WFLY-7771 > URL: https://issues.jboss.org/browse/WFLY-7771 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Environment: Centos 7/Wildfly 10.1.0.Final > Reporter: Albert Borgen > Assignee: Stuart Douglas > Priority: Critical > > 2016-10-16 21:39:04,743 ERROR [io.undertow.websockets.jsr.request] (default task-242) UT026006: Exception running web socket method: java.lang.RuntimeException: java.lang.IllegalStateException: PBOX00048: Failed to obtain ApplicationPolicy for domain other > at io.undertow.websockets.jsr.ServerWebSocketContainer.invokeEndpointMethod(ServerWebSocketContainer.java:577) > at io.undertow.websockets.jsr.ServerWebSocketContainer$6.run(ServerWebSocketContainer.java:561) > at io.undertow.websockets.jsr.OrderedExecutor$ExecutorTask.run(OrderedExecutor.java:67) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalStateException: PBOX00048: Failed to obtain ApplicationPolicy for domain other > at org.jboss.security.plugins.mapping.JBossMappingManager.getMappingContext(JBossMappingManager.java:67) > at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.setup(SecurityContextThreadSetupAction.java:110) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:42) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.websockets.jsr.ServerWebSocketContainer.invokeEndpointMethod(ServerWebSocketContainer.java:575) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2016