December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-850) Elytron ldap-realm allows access with empty password

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-850: -------------------------------- Summary: Elytron ldap-realm allows access with empty password Key: ELY-850 URL: https://issues.jboss.org/browse/ELY-850 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Blocker An empty password is treated as an anonymous login by some LDAP servers (e.g. by Microsoft Active Directory). In case when Elytron ldap-realm is configured for that type of LDAP server then access with empty password to secured web resource guarded by that ldap-realm is always granted. There should be some attribute for configuring whether empty password should be accepted by ldap-realm. Similar issue occurs in previous versions of application server, see: * https://bugzilla.redhat.com/show_bug.cgi?id=901251 * https://bugzilla.redhat.com/show_bug.cgi?id=885569 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2022) Can not invoke read-resource-description on multi target address with a resource named server.

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2022?page=com.atlassian.jira.plugi... ] Harald Pehl commented on WFCORE-2022: ------------------------------------- Similar error for {code} /subsystem=messaging-activemq/server=*/queue=*:read-resource-description { "outcome" => "failed", "result" => [], "failure-description" => "WFLYCTL0030: No resource definition is registered for address [ (\"subsystem\" => \"messaging-activemq\"), (\"server\" => \"*\") ]", "rolled-back" => true } {code} > Can not invoke read-resource-description on multi target address with a resource named server. > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-2022 > URL: https://issues.jboss.org/browse/WFCORE-2022 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha12 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > To reproduce, invoke: > {noformat} > /subsystem=undertow/server=*/http-listener=*:read-resource-description > { > "outcome" => "failed", > "result" => [], > "failure-description" => "WFLYCTL0030: No resource definition is registered for address [ > (\"subsystem\" => \"undertow\"), > (\"server\" => \"*\") > ]", > "rolled-back" => true > } > {noformat} > The address is valid but the operation fails at org.jboss.as.controller.operations.global.GlobalOperationHandlers.RegistrationAddressResolver#executeMultiTargetChildren when checking the condition: > {noformat} > if (path.getKey().equals(RUNNING_SERVER) && path.isWildcard() && newRemaining.size() > 0) > {noformat} > The check was added for WFCORE-948 but makes any multi target operation with a server resource fails (such as Undertow server or messaging-activemq server resources). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7792) Mixed domain with EAP 6.2 slave: data sources operations failed

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-7792?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-7792: -------------------------------- Priority: Optional (was: Major) > Mixed domain with EAP 6.2 slave: data sources operations failed > --------------------------------------------------------------- > > Key: WFLY-7792 > URL: https://issues.jboss.org/browse/WFLY-7792 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Optional > > Run a mixed domain where WildFly 11.0.0-SNAPSHOT is the master and *+EAP 6.2.0+* is a slave server. Operation on data source ExampleDS failed due to incompatibility of models: > {noformat} > [domain@127.0.0.100:9990 /] /host=eap620/server=server-one/subsystem=datasources/data-source=ExampleDS:test-connection-in-pool > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"host\" => \"eap620\"), > (\"server\" => \"server-one\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\") > ], > \"operation\" => \"test-connection-in-pool\", > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"ae186a65-8c76-41d0-bd23-79154b5f92f7\" > } > } at resource [ > (\"host\" => \"eap620\"), > (\"server\" => \"server-one\"), > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\") > ] to subsystem 'datasources' model version '1.2.0' -- attributes [statistics-enabled] WFLYJCA0088: Attributes [statistics-enabled] rejected. Must be true", > "rolled-back" => true, > "result" => [true] > } > {noformat} > This only happens when talking with *+EAP 6.2.0+* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2127) wildfly web management console hangs during deploy from cli

by Michal Jurc (JIRA)

Michal Jurc created WFCORE-2127: ----------------------------------- Summary: wildfly web management console hangs during deploy from cli Key: WFCORE-2127 URL: https://issues.jboss.org/browse/WFCORE-2127 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha1 Reporter: Michal Jurc We are running wildfly in domain mode with the following configuration. host A running domain controlller host B running host controller with one app sever host C running host controller with one app server host D running host controller with one app server When we deloy war using jboss-cli the web console is blocked for usage until deploy completes. I have run jvisualvm and it does not appear that domain controller process is starved for resources (cpu, memory, threads). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7817) Upgrade to Apache CXF 3.1.9

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-7817: ------------------------------------- Summary: Upgrade to Apache CXF 3.1.9 Key: WFLY-7817 URL: https://issues.jboss.org/browse/WFLY-7817 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7816) Camel CXF version not compatible with WildFly CXF

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-7816: ------------------------------------ Summary: Camel CXF version not compatible with WildFly CXF Key: WFLY-7816 URL: https://issues.jboss.org/browse/WFLY-7816 Project: WildFly Issue Type: Component Upgrade Components: Web Services Affects Versions: 10.1.0.Final Reporter: Thomas Diesler Assignee: Alessio Soldano Fix For: 10.2.0.Final, 11.0.0.Alpha1 cxf-3.1.9 distributed with camel-2.19.x is not compatible with cxf-3.1.6 from wildfly-10.1.0.Final {code} Caused by: java.lang.NoSuchMethodError: org.apache.cxf.message.Message.remove(Ljava/lang/Class;)Ljava/lang/Object; at org.apache.camel.component.cxf.CxfEndpoint$CamelCxfClientImpl.setParameters(CxfEndpoint.java:1239) at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:470) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:416) at org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:133) {code} CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1546 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-849: ------------------------------------ Summary: Rename setMechanismProperties to setSaslMechanismProperties Key: ELY-849 URL: https://issues.jboss.org/browse/ELY-849 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 1.1.0.Beta18 If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties. We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2126) Upgrade to Undertow 1.4.3+ in WFCORE 2.2.1 to resolve CVE-2016-4993

by Falko M. (JIRA)

Falko M. created WFCORE-2126: -------------------------------- Summary: Upgrade to Undertow 1.4.3+ in WFCORE 2.2.1 to resolve CVE-2016-4993 Key: WFCORE-2126 URL: https://issues.jboss.org/browse/WFCORE-2126 Project: WildFly Core Issue Type: Component Upgrade Affects Versions: 2.2.1.CR1 Reporter: Falko M. WFCORE-1688 upgraded Undertow to 1.4.0.Final which contains a rather serious sercurity vulnerability which was fixed in Undertow 1.4.3.Final (see UNDERTOW-827). WildFly Swarm already builds on top of WFCORE 2.2.1.CR1 and will probably switch to 2.2.1.Final once it is released, so from my perspective it would be very sensible to upgrade to a corrected version of Undertow in the next CR (or Final) of WFCORE 2.2.1. PS: WFCORE seems to build just fine (including tests) when upgrading the Undertow version to 1.4.7.Final in pom.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2116) Upgrade xnio to 3.4.2.Final

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2116?page=com.atlassian.jira.plugi... ] Frank Langelage commented on WFCORE-2116: ----------------------------------------- https://github.com/wildfly/wildfly-core/pull/2035 https://github.com/wildfly/wildfly-core/pull/2036 > Upgrade xnio to 3.4.2.Final > --------------------------- > > Key: WFCORE-2116 > URL: https://issues.jboss.org/browse/WFCORE-2116 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 3.0.0.Alpha15 > Reporter: Tomasz Adamski > Assignee: Frank Langelage > Fix For: 3.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2116) Upgrade xnio to 3.4.2.Final

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2116?page=com.atlassian.jira.plugi... ] Frank Langelage reassigned WFCORE-2116: --------------------------------------- Assignee: Frank Langelage (was: Tomasz Adamski) > Upgrade xnio to 3.4.2.Final > --------------------------- > > Key: WFCORE-2116 > URL: https://issues.jboss.org/browse/WFCORE-2116 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 3.0.0.Alpha15 > Reporter: Tomasz Adamski > Assignee: Frank Langelage > Fix For: 3.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 December 2016