January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5959) Infinispan caches non transactional despite transactional cache mode

by Alexander Slack (JIRA)

Alexander Slack created WFLY-5959: ------------------------------------- Summary: Infinispan caches non transactional despite transactional cache mode Key: WFLY-5959 URL: https://issues.jboss.org/browse/WFLY-5959 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR5 Reporter: Alexander Slack Assignee: Paul Ferraro Local Infinispan caches declared in standalone.xml are no longer set as transactional even if a transactional mode is selected. This prevents creation of atomic maps using AtomicMapLookup as that specifically checks if the cache is transactional (throws java.lang.IllegalStateException: AtomicMap needs a transactional cache.) Possibly caused by issue WFLY-5327. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1281) NPE in principal-to-group group searching

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1281?page=com.atlassian.jira.plugi... ] Ondrej Lukas moved WFLY-5958 to WFCORE-1281: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1281 (was: WFLY-5958) Component/s: Domain Management Security (was: Domain Management) (was: Security) Affects Version/s: 2.0.5.Final (was: 10.0.0.CR5) > NPE in principal-to-group group searching > ----------------------------------------- > > Key: WFCORE-1281 > URL: https://issues.jboss.org/browse/WFCORE-1281 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.0.5.Final > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Attachments: groupsearch.ldif > > > In case when ldap authorization with principal-to-group group searching is used in security realm and LDAP entry found by value of 'group-attribute' does not include attribute mentioned in 'group-name-attribute' then it causes authentication fail. It is caused by missing null check for groupNameAttr and hidden NPE thrown from [1]. > [1] https://github.com/wildfly/wildfly-core/blob/18393273a1c9e464fb0cc9597951... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5958) NPE in principal-to-group group searching

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5958?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-5958: -------------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > NPE in principal-to-group group searching > ----------------------------------------- > > Key: WFLY-5958 > URL: https://issues.jboss.org/browse/WFLY-5958 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 10.0.0.CR5 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Attachments: groupsearch.ldif > > > In case when ldap authorization with principal-to-group group searching is used in security realm and LDAP entry found by value of 'group-attribute' does not include attribute mentioned in 'group-name-attribute' then it causes authentication fail. It is caused by missing null check for groupNameAttr and hidden NPE thrown from [1]. > [1] https://github.com/wildfly/wildfly-core/blob/18393273a1c9e464fb0cc9597951... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5958) NPE in principal-to-group group searching

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5958?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-5958: ---------------------------------------- This code is part of WildFly Core - please move the issue over there. Thanks. > NPE in principal-to-group group searching > ----------------------------------------- > > Key: WFLY-5958 > URL: https://issues.jboss.org/browse/WFLY-5958 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 10.0.0.CR5 > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > Attachments: groupsearch.ldif > > > In case when ldap authorization with principal-to-group group searching is used in security realm and LDAP entry found by value of 'group-attribute' does not include attribute mentioned in 'group-name-attribute' then it causes authentication fail. It is caused by missing null check for groupNameAttr and hidden NPE thrown from [1]. > [1] https://github.com/wildfly/wildfly-core/blob/18393273a1c9e464fb0cc9597951... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1015) Wrong MvelConstraint compilation with Unicode class name and the same name property

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1015?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi commented on DROOLS-1015: ------------------------------------------- Thanks Mario, > My expectation is that the workaround I'm suggesting in 2. will also work for your use case. I confirmed that it works for the Unicode case, too. I updated the Workaround section accordingly. > Wrong MvelConstraint compilation with Unicode class name and the same name property > ----------------------------------------------------------------------------------- > > Key: DROOLS-1015 > URL: https://issues.jboss.org/browse/DROOLS-1015 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > If a fact has a property of Unicode class name (e.g. 住所) and the property name is the same (住所), constraint is not correctly compiled by MVEL. Internally, AbstractParser.createPropertyToken() misunderstands the property as a class name literal. > {code:java} > public class I18nPerson implements Serializable { > private 住所住所; // "address" in Japanese > public 住所 get住所() { > return 住所; > } > .... > {code} > {noformat} > when > p : I18nPerson( 住所 != null ) > {noformat} > This constraint is always evaluated to "true". > Essentially, this is not only a problem of Unicode. We can reproduce the issue by a capitalized property name. > {code:java} > public class Person implements Serializable { > private Address address; > public Address getAddress() { > return address; > } > .... > {code} > {noformat} > when > p : I18nPerson( Address != null ) > {noformat} > Of course we should use lower case letters here from JavaBeans point of view so we don't hit this issue with English usually. But some languages like Japanese cannot express "lower case/upper case" so result in this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1015) Wrong MvelConstraint compilation with Unicode class name and the same name property

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1015?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-1015: -------------------------------------- Workaround Description: A. Add "this." to the property. for example, ( 住所 != null ) -> ( this.住所 != null ) or B. Use a different property name from class name was: A. Add "this." to the property. for example, or B. Use a different property name from class name > Wrong MvelConstraint compilation with Unicode class name and the same name property > ----------------------------------------------------------------------------------- > > Key: DROOLS-1015 > URL: https://issues.jboss.org/browse/DROOLS-1015 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > If a fact has a property of Unicode class name (e.g. 住所) and the property name is the same (住所), constraint is not correctly compiled by MVEL. Internally, AbstractParser.createPropertyToken() misunderstands the property as a class name literal. > {code:java} > public class I18nPerson implements Serializable { > private 住所住所; // "address" in Japanese > public 住所 get住所() { > return 住所; > } > .... > {code} > {noformat} > when > p : I18nPerson( 住所 != null ) > {noformat} > This constraint is always evaluated to "true". > Essentially, this is not only a problem of Unicode. We can reproduce the issue by a capitalized property name. > {code:java} > public class Person implements Serializable { > private Address address; > public Address getAddress() { > return address; > } > .... > {code} > {noformat} > when > p : I18nPerson( Address != null ) > {noformat} > Of course we should use lower case letters here from JavaBeans point of view so we don't hit this issue with English usually. But some languages like Japanese cannot express "lower case/upper case" so result in this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1015) Wrong MvelConstraint compilation with Unicode class name and the same name property

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1015?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-1015: -------------------------------------- Workaround Description: * A. Add "this." to the property. for example, ( 住所 != null ) -> ( this.住所 != null ) or * B. Use a different property name from class name was: A. Add "this." to the property. for example, ( 住所 != null ) -> ( this.住所 != null ) or B. Use a different property name from class name > Wrong MvelConstraint compilation with Unicode class name and the same name property > ----------------------------------------------------------------------------------- > > Key: DROOLS-1015 > URL: https://issues.jboss.org/browse/DROOLS-1015 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > If a fact has a property of Unicode class name (e.g. 住所) and the property name is the same (住所), constraint is not correctly compiled by MVEL. Internally, AbstractParser.createPropertyToken() misunderstands the property as a class name literal. > {code:java} > public class I18nPerson implements Serializable { > private 住所住所; // "address" in Japanese > public 住所 get住所() { > return 住所; > } > .... > {code} > {noformat} > when > p : I18nPerson( 住所 != null ) > {noformat} > This constraint is always evaluated to "true". > Essentially, this is not only a problem of Unicode. We can reproduce the issue by a capitalized property name. > {code:java} > public class Person implements Serializable { > private Address address; > public Address getAddress() { > return address; > } > .... > {code} > {noformat} > when > p : I18nPerson( Address != null ) > {noformat} > Of course we should use lower case letters here from JavaBeans point of view so we don't hit this issue with English usually. But some languages like Japanese cannot express "lower case/upper case" so result in this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1015) Wrong MvelConstraint compilation with Unicode class name and the same name property

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1015?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi updated DROOLS-1015: -------------------------------------- Workaround Description: A. Add "this." to the property. for example, or B. Use a different property name from class name was:Use a different property name from class name. But it's sometimes hard to follow. > Wrong MvelConstraint compilation with Unicode class name and the same name property > ----------------------------------------------------------------------------------- > > Key: DROOLS-1015 > URL: https://issues.jboss.org/browse/DROOLS-1015 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > If a fact has a property of Unicode class name (e.g. 住所) and the property name is the same (住所), constraint is not correctly compiled by MVEL. Internally, AbstractParser.createPropertyToken() misunderstands the property as a class name literal. > {code:java} > public class I18nPerson implements Serializable { > private 住所住所; // "address" in Japanese > public 住所 get住所() { > return 住所; > } > .... > {code} > {noformat} > when > p : I18nPerson( 住所 != null ) > {noformat} > This constraint is always evaluated to "true". > Essentially, this is not only a problem of Unicode. We can reproduce the issue by a capitalized property name. > {code:java} > public class Person implements Serializable { > private Address address; > public Address getAddress() { > return address; > } > .... > {code} > {noformat} > when > p : I18nPerson( Address != null ) > {noformat} > Of course we should use lower case letters here from JavaBeans point of view so we don't hit this issue with English usually. But some languages like Japanese cannot express "lower case/upper case" so result in this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5958) NPE in principal-to-group group searching

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-5958?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-5958: ------------------------------- Affects Version/s: 10.0.0.CR5 > NPE in principal-to-group group searching > ----------------------------------------- > > Key: WFLY-5958 > URL: https://issues.jboss.org/browse/WFLY-5958 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 10.0.0.CR5 > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > Attachments: groupsearch.ldif > > > In case when ldap authorization with principal-to-group group searching is used in security realm and LDAP entry found by value of 'group-attribute' does not include attribute mentioned in 'group-name-attribute' then it causes authentication fail. It is caused by missing null check for groupNameAttr and hidden NPE thrown from [1]. > [1] https://github.com/wildfly/wildfly-core/blob/18393273a1c9e464fb0cc9597951... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5958) NPE in principal-to-group group searching

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-5958: ---------------------------------- Summary: NPE in principal-to-group group searching Key: WFLY-5958 URL: https://issues.jboss.org/browse/WFLY-5958 Project: WildFly Issue Type: Bug Components: Domain Management, Security Reporter: Ondrej Lukas Assignee: Brian Stansberry In case when ldap authorization with principal-to-group group searching is used in security realm and LDAP entry found by value of 'group-attribute' does not include attribute mentioned in 'group-name-attribute' then it causes authentication fail. It is caused by missing null check for groupNameAttr and hidden NPE thrown from [1]. [1] https://github.com/wildfly/wildfly-core/blob/18393273a1c9e464fb0cc9597951... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016