November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7599) PersistentResourceXMLDescription for parsing/marshaling of Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7599?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-7599: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > PersistentResourceXMLDescription for parsing/marshaling of Elytron > ------------------------------------------------------------------ > > Key: WFLY-7599 > URL: https://issues.jboss.org/browse/WFLY-7599 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Optional > > Using PersistentResourceXMLDescription for parsing/marshaling of Elytron subsystem model parts would simplify code of the subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7599) PersistentResourceXMLDescription for parsing/marshaling of Elytron

by Jan Kalina (JIRA)

Jan Kalina created WFLY-7599: -------------------------------- Summary: PersistentResourceXMLDescription for parsing/marshaling of Elytron Key: WFLY-7599 URL: https://issues.jboss.org/browse/WFLY-7599 Project: WildFly Issue Type: Bug Components: Security Reporter: Jan Kalina Assignee: Darran Lofthouse Priority: Optional Using PersistentResourceXMLDescription for parsing/marshaling of Elytron subsystem model parts would simplify code of the subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1361) Infinite loop when updating a fact inside a shared subnetwork

by Alessandro Lazarotti (JIRA)

Alessandro Lazarotti created DROOLS-1361: -------------------------------------------- Summary: Infinite loop when updating a fact inside a shared subnetwork Key: DROOLS-1361 URL: https://issues.jboss.org/browse/DROOLS-1361 Project: Drools Issue Type: Bug Components: core engine Reporter: Alessandro Lazarotti Assignee: Mario Fusco Priority: Critical Updating a fact evaluated inside a shared subnetwork may cause an infinite loop as demonstrated by the following unit test: {code} @Test(timeout = 10000L) public void testUpdateOnSharedSubnetwork() { String drl = "import " + AtomicInteger.class.getCanonicalName() + ";\n" + "global java.util.List list;\n" + "rule R1y when\n" + " AtomicInteger() \n" + " Number() from accumulate ( AtomicInteger( ) and $s : String( ) ; count($s) )" + " eval(false)\n" + "then\n" + "end\n" + "\n" + "rule R2 when\n" + " $i : AtomicInteger( get() < 3 )\n" + "then\n" + " $i.incrementAndGet();" + " insert(\"test\" + $i.get());" + " update($i);" + "end\n" + "\n" + "rule R1x when\n" + " AtomicInteger() \n" + " $c : Number() from accumulate ( AtomicInteger( ) and $s : String( ) ; count($s) )\n" + " eval(true)\n" + "then\n" + " list.add($c);" + "end\n"; KieSession kieSession = new KieHelper().addContent( drl, ResourceType.DRL ) .build().newKieSession(); List<Number> list = new ArrayList<Number>(); kieSession.setGlobal( "list", list ); kieSession.insert( new AtomicInteger( 0 ) ); kieSession.insert( "test" ); kieSession.fireAllRules(); assertEquals(1, list.size()); assertEquals(4, list.get(0).intValue()); } {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1360) Infinite loop when updating a fact inside a shared subnetwork

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1360: ----------------------------------- Summary: Infinite loop when updating a fact inside a shared subnetwork Key: DROOLS-1360 URL: https://issues.jboss.org/browse/DROOLS-1360 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco Priority: Critical Updating a fact evaluated inside a shared subnetwork may cause an infinite loop as demonstrated by the following unit test: {code} @Test(timeout = 10000L) public void testUpdateOnSharedSubnetwork() { String drl = "import " + AtomicInteger.class.getCanonicalName() + ";\n" + "global java.util.List list;\n" + "rule R1y when\n" + " AtomicInteger() \n" + " Number() from accumulate ( AtomicInteger( ) and $s : String( ) ; count($s) )" + " eval(false)\n" + "then\n" + "end\n" + "\n" + "rule R2 when\n" + " $i : AtomicInteger( get() < 3 )\n" + "then\n" + " $i.incrementAndGet();" + " insert(\"test\" + $i.get());" + " update($i);" + "end\n" + "\n" + "rule R1x when\n" + " AtomicInteger() \n" + " $c : Number() from accumulate ( AtomicInteger( ) and $s : String( ) ; count($s) )\n" + " eval(true)\n" + "then\n" + " list.add($c);" + "end\n"; KieSession kieSession = new KieHelper().addContent( drl, ResourceType.DRL ) .build().newKieSession(); List<Number> list = new ArrayList<Number>(); kieSession.setGlobal( "list", list ); kieSession.insert( new AtomicInteger( 0 ) ); kieSession.insert( "test" ); kieSession.fireAllRules(); assertEquals(1, list.size()); assertEquals(4, list.get(0).intValue()); } {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-745) Using attribute name instead of OID in x500-attribute-principal-decoder

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-745?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-745: --------------------------------- I like the idea of a simple properties-file database as proposed. I think we'll still need constants for them though, as otherwise we'll have to do things like: {code} String cnOid = OidDatabaseThingy.getOidByName("cn"); {code} I think we can initialize the constants from the database though, going forward. As far as conflicts go, yes OIDs are unique, however the string names may not be globally unique (though within LDAP at least, they should be). Note that we use OIDs for a wide variety of other purposes than LDAP though. > Using attribute name instead of OID in x500-attribute-principal-decoder > ----------------------------------------------------------------------- > > Key: ELY-745 > URL: https://issues.jboss.org/browse/ELY-745 > Project: WildFly Elytron > Issue Type: Bug > Components: X.500 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > > Using OIDs not really convenient. > See description of JBEAP-6100 for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-752) Coverity static analysis: Dereference null return value in SerializedPermissionCollection (Elytron)

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-752?page=com.atlassian.jira.plugin.sy... ] Josef Cacek commented on ELY-752: --------------------------------- Thanks David, it was updated in the Scan results.. https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=59110... > Coverity static analysis: Dereference null return value in SerializedPermissionCollection (Elytron) > --------------------------------------------------------------------------------------------------- > > Key: ELY-752 > URL: https://issues.jboss.org/browse/ELY-752 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Labels: static_analysis > > Coverity static-analysis scan found possible use of null object comming from {{SerializedPermissionCollection.readResolve()}} method. > https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57600... > The {{newPermissionCollection()}} call may return null in the code: > {code} > final PermissionCollection collection = s.newPermissionCollection(); > {code} > It's than used without a null-check in the method: > {code} > for (Permission permission : p) { > collection.add(permission); > } > if (r) collection.setReadOnly(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1985: ------------------------------------------ I prefer the sort simply by name, excluding group. But, we need to understand why we are getting the sorting we are seeing and then discuss what might change if we adjust things. Perhaps there is something about iiop that causes group to not matter to the r-r sorting, but it does matter elsewhere. We need to understand that. > :read-resource-description operation should consistently order resources by alphabet > ------------------------------------------------------------------------------------ > > Key: WFCORE-1985 > URL: https://issues.jboss.org/browse/WFCORE-1985 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Michal Jurc > Assignee: Ken Wills > > While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet). > Affected resources: > * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1992) CLI inconsistently parse {} in another object as UNDEFINED

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1992?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-1992: ------------------------------- Description: CLI interprets {} as blank object in resource attribute (correct), but as UNDEFINED in object attribute. (in model parameter of *performRuntime* of ADD operation) {code:java} /subsystem=elytron/properties-realm=realm:add(users-properties={path=$SOME_PATH},groups-properties={}) => groups-properties = OBJECT {} {code} {code:java} /subsystem=elytron/ldap-realm=ldap-realm8:add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) => otp-credential-mapper=UNDEFINED {code} was: CLI interprets {} as blank object in resource attribute, but as UNDEFINED in object attribute. (in model parameter of *performRuntime* of ADD operation) {code:java} /subsystem=elytron/properties-realm=realm:add(users-properties={path=$SOME_PATH},groups-properties={}) => groups-properties = OBJECT {} {code} {code:java} /subsystem=elytron/ldap-realm=ldap-realm8:add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) => otp-credential-mapper=UNDEFINED {code} > CLI inconsistently parse {} in another object as UNDEFINED > ---------------------------------------------------------- > > Key: WFCORE-1992 > URL: https://issues.jboss.org/browse/WFCORE-1992 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha12 > Reporter: Jan Kalina > Priority: Minor > > CLI interprets {} as blank object in resource attribute (correct), but as UNDEFINED in object attribute. (in model parameter of *performRuntime* of ADD operation) > {code:java} > /subsystem=elytron/properties-realm=realm:add(users-properties={path=$SOME_PATH},groups-properties={}) > => groups-properties = OBJECT {} > {code} > {code:java} > /subsystem=elytron/ldap-realm=ldap-realm8:add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) > => otp-credential-mapper=UNDEFINED > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1992) CLI inconsistently parse {} in another object as UNDEFINED

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1992?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-1992: ------------------------------- Description: CLI interprets {} as blank object in resource attribute, but as UNDEFINED in object attribute. (in model parameter of *performRuntime* of ADD operation) {code:java} /subsystem=elytron/properties-realm=realm:add(users-properties={path=$SOME_PATH},groups-properties={}) => groups-properties = OBJECT {} {code} {code:java} /subsystem=elytron/ldap-realm=ldap-realm8:add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) => otp-credential-mapper=UNDEFINED {code} was: CLI interprets {code:java} /subsystem=elytron/properties-realm=realm:add(users-properties={path=$SOME_PATH},groups-properties={}) {code} with *groups-properties=OBJECT{}* in input of performRuntime() of ADD operation. But if the {} is inside of another object, it gives *otp-credential-mapper=UNDEFINED* instead... {code:java} /subsystem=elytron/ldap-realm=ldap-realm8:add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) {code} > CLI inconsistently parse {} in another object as UNDEFINED > ---------------------------------------------------------- > > Key: WFCORE-1992 > URL: https://issues.jboss.org/browse/WFCORE-1992 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha12 > Reporter: Jan Kalina > Priority: Minor > > CLI interprets {} as blank object in resource attribute, but as UNDEFINED in object attribute. (in model parameter of *performRuntime* of ADD operation) > {code:java} > /subsystem=elytron/properties-realm=realm:add(users-properties={path=$SOME_PATH},groups-properties={}) > => groups-properties = OBJECT {} > {code} > {code:java} > /subsystem=elytron/ldap-realm=ldap-realm8:add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) > => otp-credential-mapper=UNDEFINED > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1992) CLI inconsistently parse {} in another object as UNDEFINED

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1992?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-1992: ------------------------------- Affects Version/s: 3.0.0.Alpha12 > CLI inconsistently parse {} in another object as UNDEFINED > ---------------------------------------------------------- > > Key: WFCORE-1992 > URL: https://issues.jboss.org/browse/WFCORE-1992 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha12 > Reporter: Jan Kalina > Priority: Minor > > CLI interprets > {code:java} > /subsystem=elytron/properties-realm=realm:add(users-properties={path=$SOME_PATH},groups-properties={}) > {code} > with *groups-properties=OBJECT{}* in input of performRuntime() of ADD operation. > But if the {} is inside of another object, it gives *otp-credential-mapper=UNDEFINED* instead... > {code:java} > /subsystem=elytron/ldap-realm=ldap-realm8:add(dir-context=local-ldap,identity-mapping={rdn-identifier=uid,otp-credential-mapper={}}) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016