August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3269) XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3269?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3269: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1133961|https://bugzilla.redhat.com/show_bug.cgi?id=1133961] from POST to MODIFIED > XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value. > ------------------------------------------------------------------------------------------------- > > Key: WFLY-3269 > URL: https://issues.jboss.org/browse/WFLY-3269 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Emmanuel Hugonnet > Fix For: 9.0.0.Beta1 > > > {code} > Trying so, I run in the error (when starting WildFly) : > 10:28:29,674 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[76,25] > Message: JBAS014724: Missing required attribute(s): FORCE > at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:134) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.domain.management.parsing.ManagementXml.parseUsernameToDn_2_0(ManagementXml.java:2118) [wildfly-domain-management-8.0.0.Final.jar:8.0.0.Final] > {code} > {code} > <security-realm name="MgtRealm"> > <authentication> > <ldap connection="ovodavLDAP" base-dn="ou=People,dc=hydrogenic,dc=local"> >  > <username-filter attribute="uid"/> > </ldap> > </authentication> > <authorization> > <ldap connection="ovodavLDAP"> > <username-to-dn> > <username-filter base-dn="ou=People,dc=hydrogenic,dc=local" recursive="false" attribute="uid" user-dn-attribute="dn" /> > </username-to-dn> > <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="uid"> > <group-to-principal base-dn="ou=Groups,dc=hydrogenic,dc=local" recursive="true" search-by="DISTINGUISHED_NAME"> > <membership-filter principal-attribute="uniqueMember" /> > </group-to-principal> > </group-search> > </ldap> > </authorization> > </security-realm> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-950) RESTEasy: Empty cfg. param javax.ws.rs.Application produces exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-950?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-950: ---------------------------------------------- Weinan Li <weli(a)redhat.com> changed the Status of [bug 899666|https://bugzilla.redhat.com/show_bug.cgi?id=899666] from ASSIGNED to MODIFIED > RESTEasy: Empty cfg. param javax.ws.rs.Application produces exception > --------------------------------------------------------------------- > > Key: WFLY-950 > URL: https://issues.jboss.org/browse/WFLY-950 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Pavel Janousek > Assignee: Weinan Li > > RESTEasy can be configured through several configuration options in WAR application deployment file WEB-INF/web.xml. The major one (also portable defined by JAX-RS standard) is _javax.ws.rs.Application_. When I set this parameter to empty content present behavior is raising exception "java.lang.StringIndexOutOfBoundsException: String index out of range: 0", it is not so good. > I think, this is hard miss-configuration error and deployment description as this one should be rejected and a such application should not be deployed at all with appropriate error message, but not only by messed exception. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3716) Upgrade JAXB to 2.2.5.jboss-2 for bug fixes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3716?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3716: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> changed the Status of [bug 1127327|https://bugzilla.redhat.com/show_bug.cgi?id=1127327] from ON_QA to VERIFIED > Upgrade JAXB to 2.2.5.jboss-2 for bug fixes > ------------------------------------------- > > Key: WFLY-3716 > URL: https://issues.jboss.org/browse/WFLY-3716 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: XML Frameworks > Reporter: Paul Gier > Assignee: Paul Gier > > Upgrade jaxb to 2.2.5.jboss-2 to include some bug fixes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-851) Base64Utils class cuts leading zeroes from encoded bytes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-851?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-851: -------------------------------------------------- Peter Skopek <pskopek(a)redhat.com> changed the Status of [bug 1125004|https://bugzilla.redhat.com/show_bug.cgi?id=1125004] from NEW to ASSIGNED > Base64Utils class cuts leading zeroes from encoded bytes > -------------------------------------------------------- > > Key: SECURITY-851 > URL: https://issues.jboss.org/browse/SECURITY-851 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: PicketBox_4_0_21.Beta2 > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Blocker > > Vault util is failing for some password/salt/iteration combinations because Base64Utils class strips zeroes from provided byte array. > So if a user encodes a key with length 8 and the leading byte of the key is zero, then after decoding he only gets 7 (or less) bytes. > For instance: > {code} > encode ( { 0, 81, 121, -37, 46, -64, 20, 114 } ) -> "1HUTikm1Ho" > decode ("1HUTikm1Ho") -> { 81, 121, -37, 46, -64, 20, 114 } > {code} > As a result the PBEUtil will fail with javax.crypto.IllegalBlockSizeException. > IMHO the same problem can occur on other places where the Base64Utils class is used (not only the Vault). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-479) Pseudo Clock doesn't work for 2 not statements

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-479?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-479: ------------------------------------------------ Radovan Synek <rsynek(a)redhat.com> changed the Status of [bug 1122738|https://bugzilla.redhat.com/show_bug.cgi?id=1122738] from ASSIGNED to VERIFIED > Pseudo Clock doesn't work for 2 not statements > ---------------------------------------------- > > Key: DROOLS-479 > URL: https://issues.jboss.org/browse/DROOLS-479 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final, 6.1.0.Beta3 > Environment: linux 14.04 > Reporter: Richard Ambridge > Assignee: Mario Fusco > Labels: pseudoclock > > If a rule (event) has the following: > + "when\n" > + " $s : Cheese(type==\"stinky\")\n" > + " not( Cheese(type==\"a\", this after [0s,3s] $s ) )\n" > + " not( Cheese(type==\"b\", this after [0s,5s] $s ) )\n" //2 * not > and pseudo clock is used, the rule doesn't fire. > If realtime clock is used, the rule works. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections

by ofbiz brazil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ] ofbiz brazil commented on WFLY-3791: ------------------------------------ Yes, I am really using the last version of Wildfly 8.1.0.Final, as I described in bug ticket. :) Could you replicate this error in your java code? > Error on ModelControllerClient to list sections > ----------------------------------------------- > > Key: WFLY-3791 > URL: https://issues.jboss.org/browse/WFLY-3791 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.1.0.Final > Environment: Java 7 > Reporter: ofbiz brazil > Assignee: Darran Lofthouse > > Hello, > When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine. > Java Code: > -------------- > final ModelNode request = new ModelNode(); > request.get(ClientConstants.OP).set("read-resource"); > request.get("recursive").set(true); > request.get(ClientConstants.OP_ADDR).add("subsystem", "security"); > final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999); > final ModelNode response = client.execute(new OperationBuilder(request).build()); > final String section = response.get(ClientConstants.RESULT).get("security-domain") > .get("pw_MSSQL_CAS_DS") > Result: > --------- > { > "outcome" => "failed", > "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found", > "rolled-back" => true > } > Cheers, -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-584) CDIHelper caches JNDI lookup early on, missing on java:comp/BeanManager

by Antoine Toulme (JIRA)

[ https://issues.jboss.org/browse/DROOLS-584?page=com.atlassian.jira.plugin... ] Antoine Toulme updated DROOLS-584: ---------------------------------- Description: Looking at CDIHelper, on line 96, it caches a static beanCreator. The beanCreator is created based on JNDI lookups for CDI BeanManager. The JNDI lookup returns null however, in the situation where the system just started out, especially when the system is modular. For example Wildfly 8.1 will create such a situation. In the event that the BeanManager is not there, the default implementation of using a reflection approach is used instead, which transparently masks the problem. However, if the bean created relies on CDI to inject fields, it becomes problematic. A few recommendations: -do not cache the beanCreator. Recreate it every time, at the cost of making several JNDI lookups. -use DeltaSpike, longer term plan to remove this code. > CDIHelper caches JNDI lookup early on, missing on java:comp/BeanManager > ----------------------------------------------------------------------- > > Key: DROOLS-584 > URL: https://issues.jboss.org/browse/DROOLS-584 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Final, 6.2.0.Beta1 > Reporter: Antoine Toulme > Assignee: Mark Proctor > > Looking at CDIHelper, on line 96, it caches a static beanCreator. The beanCreator is created based on JNDI lookups for CDI BeanManager. > The JNDI lookup returns null however, in the situation where the system just started out, especially when the system is modular. For example Wildfly 8.1 will create such a situation. > In the event that the BeanManager is not there, the default implementation of using a reflection approach is used instead, which transparently masks the problem. > However, if the bean created relies on CDI to inject fields, it becomes problematic. > A few recommendations: > -do not cache the beanCreator. Recreate it every time, at the cost of making several JNDI lookups. > -use DeltaSpike, longer term plan to remove this code. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-584) CDIHelper caches JNDI lookup early on, missing on java:comp/BeanManager

by Antoine Toulme (JIRA)

Antoine Toulme created DROOLS-584: ------------------------------------- Summary: CDIHelper caches JNDI lookup early on, missing on java:comp/BeanManager Key: DROOLS-584 URL: https://issues.jboss.org/browse/DROOLS-584 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.2.0.Beta1, 6.1.0.Final Reporter: Antoine Toulme Assignee: Mark Proctor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1260) Remove workaround for shutting down the ModelControllerClientOperationHandlers

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1260?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-1260: -------------------------------------- I don't think this really relates to graceful shutdown, which is focussed on user requests rather than management operations. > Remove workaround for shutting down the ModelControllerClientOperationHandlers > ------------------------------------------------------------------------------ > > Key: WFLY-1260 > URL: https://issues.jboss.org/browse/WFLY-1260 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Emanuel Muckenhuber > > Once the graceful shutdown API is in place we need to cleanup the way the ModelControllerClientOperationHandler channels are closed. Currently we are waiting for all current operations to complete, in order that the response for :reload / :shutdown operations are sent. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3793) Implement transformers for graceful shutdown operations

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-3793: ------------------------------------ Summary: Implement transformers for graceful shutdown operations Key: WFLY-3793 URL: https://issues.jboss.org/browse/WFLY-3793 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 August 2014