July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3067) add-alias for credential store might fail when executed in the same batch operation with credential store creation

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3067?page=com.atlassian.jira.plugi... ] Lin Gao moved JBEAP-12147 to WFCORE-3067: ----------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3067 (was: JBEAP-12147) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.1.0.DR19) > add-alias for credential store might fail when executed in the same batch operation with credential store creation > ------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3067 > URL: https://issues.jboss.org/browse/WFCORE-3067 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Lin Gao > Assignee: Lin Gao > Labels: elytron > Original Estimate: 3 days > Remaining Estimate: 3 days > > When creating in single batch command credential store and adding aliases to it, it often fails with \[1\] (depending on machine speed) indicating that credential store is not yet up and running. I guess this is somehow related to runtime-only operations. > I believe this should work in batch operations. If it is not possible this needs to be at least very well documented. > \[1\] > {noformat} > 10:49:03,633 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add-alias") failed - address: ([ > ("subsystem" => "elytron"), > ("credential-store" => "cred-store") > ]) - failure description: "WFLYELY00007: The required service 'service org.wildfly.security.credential-store.cred-store' is not UP, it is currently 'STARTING'." > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-126) Reports should list duplicate id's and messages only once

by James Perkins (JIRA)

James Perkins created LOGTOOL-126: ------------------------------------- Summary: Reports should list duplicate id's and messages only once Key: LOGTOOL-126 URL: https://issues.jboss.org/browse/LOGTOOL-126 Project: Log Tool Issue Type: Bug Reporter: James Perkins Assignee: James Perkins Currently if a message is inherited on a method the report will generate an entry for every method. If the message is inherited the report should ignore the method. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1386) NPE in org.drools.core.common.TupleSetsImpl.setNextTuple

by Arkady Syamtomov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1386?page=com.atlassian.jira.plugi... ] Arkady Syamtomov commented on DROOLS-1386: ------------------------------------------ [~mfusco] maybe a hint: if we change the salience in the rule body to ANY positive number, e.g.: salience 1 and deploy the rule again, the problem disappears. > NPE in org.drools.core.common.TupleSetsImpl.setNextTuple > -------------------------------------------------------- > > Key: DROOLS-1386 > URL: https://issues.jboss.org/browse/DROOLS-1386 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final, 7.0.0.Beta4 > Reporter: Arkady Syamtomov > Assignee: Mario Fusco > Priority: Critical > > In our integration tests which were perfectly running with drools 6.3.0.Final, now we have failures with the following exception during the rules evaluation: > java.lang.NullPointerException: null > at org.drools.core.common.TupleSetsImpl.setNextTuple(TupleSetsImpl.java:349) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.TupleSetsImpl.removeUpdate(TupleSetsImpl.java:205) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.TupleSetsImpl.addDelete(TupleSetsImpl.java:110) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.reteoo.QueryElementNode$UnificationNodeViewChangedEventListener.rowRemoved(QueryElementNode.java:444) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.PhreakQueryTerminalNode.doLeftDeletes(PhreakQueryTerminalNode.java:154) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.PhreakQueryTerminalNode.doNode(PhreakQueryTerminalNode.java:46) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:282) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.evalStackEntry(RuleNetworkEvaluator.java:198) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:141) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:970) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1312) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1251) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1364) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1355) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1346) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:109) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:36) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:137) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:51) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatelessKnowledgeSessionImpl.execute(StatelessKnowledgeSessionImpl.java:254) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1386) NPE in org.drools.core.common.TupleSetsImpl.setNextTuple

by Arkady Syamtomov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1386?page=com.atlassian.jira.plugi... ] Arkady Syamtomov commented on DROOLS-1386: ------------------------------------------ [~mfusco] I created a reproducible test case for the issue. Please, check out the spring boot project from GitHub: https://github.com/icejumper/droolsstage.git In order to reproduce the issue, it's sufficient to run from the project folder: 1. mvn clean package 2. java -jar target/drools-stage-1.0-SNAPSHOT.war In the browser: http://localhost:8080 just run the 1. /deployRule/ with pre-populated drl: this will deploy the specified rule to a running instance of the rule engine. Should deploy Ok. 2. /evaluate/ this results in NPE like reported in the body of the issue Please be aware, that the project uses drools 7.0.0.Final You may try 6.5.0.Final (changing in the pom), but the result is the same. With 6.3.0.Final the issue disappears and the rule evaluation runs correctly. > NPE in org.drools.core.common.TupleSetsImpl.setNextTuple > -------------------------------------------------------- > > Key: DROOLS-1386 > URL: https://issues.jboss.org/browse/DROOLS-1386 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final, 7.0.0.Beta4 > Reporter: Arkady Syamtomov > Assignee: Mario Fusco > Priority: Critical > > In our integration tests which were perfectly running with drools 6.3.0.Final, now we have failures with the following exception during the rules evaluation: > java.lang.NullPointerException: null > at org.drools.core.common.TupleSetsImpl.setNextTuple(TupleSetsImpl.java:349) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.TupleSetsImpl.removeUpdate(TupleSetsImpl.java:205) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.TupleSetsImpl.addDelete(TupleSetsImpl.java:110) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.reteoo.QueryElementNode$UnificationNodeViewChangedEventListener.rowRemoved(QueryElementNode.java:444) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.PhreakQueryTerminalNode.doLeftDeletes(PhreakQueryTerminalNode.java:154) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.PhreakQueryTerminalNode.doNode(PhreakQueryTerminalNode.java:46) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:282) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.evalStackEntry(RuleNetworkEvaluator.java:198) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:141) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:970) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1312) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1251) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1364) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1355) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1346) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:109) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:36) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:137) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:51) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] > at org.drools.core.impl.StatelessKnowledgeSessionImpl.execute(StatelessKnowledgeSessionImpl.java:254) ~[drools-core-6.5.0.Final-redhat-2.jar:6.5.0.Final-redhat-2] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9089) Security identity not propagated into asynchronous task (elytron)

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9089?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-9089: ----------------------------- Component/s: EE (was: Remoting) > Security identity not propagated into asynchronous task (elytron) > ----------------------------------------------------------------- > > Key: WFLY-9089 > URL: https://issues.jboss.org/browse/WFLY-9089 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > *AsynchronousSecurityTestCase* fails because because anonymous user is used to call asynchronous EJB method requiring given role. > Looks like *identity is lost when creating new thread in JBossThreadFactory* - code in new thread run with anonymous identity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9089) Security identity not propagated into asynchronous task (elytron)

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9089?page=com.atlassian.jira.plugin.... ] Jan Kalina moved JBEAP-12145 to WFLY-9089: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9089 (was: JBEAP-12145) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Remoting (was: Remoting) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.ER1) > Security identity not propagated into asynchronous task (elytron) > ----------------------------------------------------------------- > > Key: WFLY-9089 > URL: https://issues.jboss.org/browse/WFLY-9089 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > *AsynchronousSecurityTestCase* fails because because anonymous user is used to call asynchronous EJB method requiring given role. > Looks like *identity is lost when creating new thread in JBossThreadFactory* - code in new thread run with anonymous identity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9088) org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase#test incorrectly resolves URLs for modules

by Radim Hatlapatka (JIRA)

Radim Hatlapatka created WFLY-9088: -------------------------------------- Summary: org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase#test incorrectly resolves URLs for modules Key: WFLY-9088 URL: https://issues.jboss.org/browse/WFLY-9088 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 11.0.0.Alpha1 Reporter: Radim Hatlapatka Assignee: Radim Hatlapatka -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9087) org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase#test incorrectly resolves URLs for modules

by Radim Hatlapatka (JIRA)

Radim Hatlapatka created WFLY-9087: -------------------------------------- Summary: org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase#test incorrectly resolves URLs for modules Key: WFLY-9087 URL: https://issues.jboss.org/browse/WFLY-9087 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 11.0.0.Alpha1 Reporter: Radim Hatlapatka Assignee: Radim Hatlapatka -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3066) Elytron subsystem - wrong description of ldap-realm.otp-credential-mapper.hash-from attribute

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3066?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-3066: ------------------------------------ Assignee: Yeray Borges (was: Darran Lofthouse) > Elytron subsystem - wrong description of ldap-realm.otp-credential-mapper.hash-from attribute > --------------------------------------------------------------------------------------------- > > Key: WFCORE-3066 > URL: https://issues.jboss.org/browse/WFCORE-3066 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Yeray Borges > > The {{hash-from}} attribute has a wrong decription in elytron subsystem. It wrongly suggests it's rather about function/algorithm name than a hash value. > {noformat} > [standalone@embedded /] /subsystem=elytron/ldap-realm=*:read-resource-description() > ... > "hash-from" => { > "type" => STRING, > "description" => "The name of the LDAP attribute of OTP hash function.", > "expressions-allowed" => true, > "required" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > }, > ... > {noformat} > The attribute should not talk about the *hash function*, but rather *hash* (or *hash value*). > _Updated_ > The description has to also mention the value of the LDAP attribute is Base64 encoded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1288) Elytron: OTP seed as byte array instead of String

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ELY-1288?page=com.atlassian.jira.plugin.s... ] Yeray Borges resolved ELY-1288. ------------------------------- Fix Version/s: 1.1.0.CR3 Resolution: Duplicate Issue Solved as duplicated. See ELY-1268 > Elytron: OTP seed as byte array instead of String > ------------------------------------------------- > > Key: ELY-1288 > URL: https://issues.jboss.org/browse/ELY-1288 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Yeray Borges > Fix For: 1.1.0.CR3 > > > The {{org.wildfly.security.password.interfaces.OneTimePassword}} interface contains {{getSeed()}} method which is of type {{byte[]}}. The more proper type seems to be a {{String}} (or {{char[]}}). > The {{OneTimePassword}} interface type description says: > bq. A one-time password, used by the OTP SASL mechanism. > The [OTP RFC 2289|https://tools.ietf.org/html/rfc2289] says > {noformat} > The seed MUST consist of purely alphanumeric characters and MUST be > of one to 16 characters in length. The seed is a string of characters > that MUST not contain any blanks and SHOULD consist of strictly > alphanumeric characters from the ISO-646 Invariant Code Set. The > seed MUST be case insensitive and MUST be internally converted to > lower case before it is processed. > {noformat} > *Suggested fix:* > Change the {{getSeed()}} method type to String. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2017