May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1179) Support safe overriding of cipher suites defined for SSLContext

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1179?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1179: --------------------------------------- This should probably go one step further so the supported cipher suites returned should be as a result of the applied cipher suite filter, any clients should only be enabling cipher suites from the supported list anyway. > Support safe overriding of cipher suites defined for SSLContext > --------------------------------------------------------------- > > Key: ELY-1179 > URL: https://issues.jboss.org/browse/ELY-1179 > Project: WildFly Elytron > Issue Type: Task > Components: SSL > Reporter: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > Clients using a wrapped SSLContext may want to further restrict the cipher suites offered, we should allow this by mapping to a union of those enabled by our configuration and those specified by the calling client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1350) Distributed statisics number varies among nodes (distributed workmanager

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1350?page=com.atlassian.jira.plugin... ] Stefano Maestri moved JBEAP-11029 to JBJCA-1350: ------------------------------------------------ Project: IronJacamar (was: JBoss Enterprise Application Platform) Key: JBJCA-1350 (was: JBEAP-11029) Workflow: classic default workflow (was: CDW with loose statuses v1) Component/s: Core (was: JCA) Affects Version/s: 1.4.4 (was: 7.1.0.DR17) > Distributed statisics number varies among nodes (distributed workmanager > ------------------------------------------------------------------------ > > Key: JBJCA-1350 > URL: https://issues.jboss.org/browse/JBJCA-1350 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.4.4 > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 1.4.5 > > > Reproducing test in https://github.com/LittleJohnII/wildfly/tree/eap7-495 > {noformat} > # build WFLY first > cd testsuite/integration/basic > mvn clean test -Dtest='Dwm*TestCase' -Djboss.server.config.file.name=standalone-ha.xml -DtrimStackTrace=false -Darquillian.launch=distributed-group > {noformat} > All the cases contain checks for distributed statistics and in some cases, these show unexpected numbers (usually, at least one test method fails for each case). For example, scheduling two work instances would produce distributed stats =2 for node1 and =3 for node 2. > I already mentioned this to [~maeste], so this is mainly a tracker. > This is a minor hamper to test writing for EAP7-495, but doesn't block it (not severe enough) - if this isn't resolved before I create a PR for tests, I'll have to comment out the distributed statistics checks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1350) Distributed statisics number varies among nodes (distributed workmanager

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1350?page=com.atlassian.jira.plugin... ] Stefano Maestri updated JBJCA-1350: ----------------------------------- Fix Version/s: 1.4.5 > Distributed statisics number varies among nodes (distributed workmanager > ------------------------------------------------------------------------ > > Key: JBJCA-1350 > URL: https://issues.jboss.org/browse/JBJCA-1350 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.4.4 > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 1.4.5 > > > Reproducing test in https://github.com/LittleJohnII/wildfly/tree/eap7-495 > {noformat} > # build WFLY first > cd testsuite/integration/basic > mvn clean test -Dtest='Dwm*TestCase' -Djboss.server.config.file.name=standalone-ha.xml -DtrimStackTrace=false -Darquillian.launch=distributed-group > {noformat} > All the cases contain checks for distributed statistics and in some cases, these show unexpected numbers (usually, at least one test method fails for each case). For example, scheduling two work instances would produce distributed stats =2 for node1 and =3 for node 2. > I already mentioned this to [~maeste], so this is mainly a tracker. > This is a minor hamper to test writing for EAP7-495, but doesn't block it (not severe enough) - if this isn't resolved before I create a PR for tests, I'll have to comment out the distributed statistics checks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-1180) Ensure a cipher suite filter for HTTP/2 compatible cipher suites can be specified.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1180?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1180: ------------------------------------- Assignee: (was: Darran Lofthouse) > Ensure a cipher suite filter for HTTP/2 compatible cipher suites can be specified. > ---------------------------------------------------------------------------------- > > Key: ELY-1180 > URL: https://issues.jboss.org/browse/ELY-1180 > Project: WildFly Elytron > Issue Type: Task > Components: SSL > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta45 > > > This may be more verification but we should ensure we can return an SSLContext optimised for HTTP/2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-1180) Ensure a cipher suite filter for HTTP/2 compatible cipher suites can be specified.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1180: ------------------------------------- Summary: Ensure a cipher suite filter for HTTP/2 compatible cipher suites can be specified. Key: ELY-1180 URL: https://issues.jboss.org/browse/ELY-1180 Project: WildFly Elytron Issue Type: Task Components: SSL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta45 This may be more verification but we should ensure we can return an SSLContext optimised for HTTP/2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-99) Tooling for C* setup, configuration and debug

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-99: ---------------------------------------- Summary: Tooling for C* setup, configuration and debug Key: HAWKULARQE-99 URL: https://issues.jboss.org/browse/HAWKULARQE-99 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Michael Foley Priority: Minor Developers idea from F2F meetings May 2017. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2362) Regression: Legacy LDAP security-realm reads system-property only during boot

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2362?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-2362. -------------------------------------- Fix Version/s: 3.0.0.Beta23 Resolution: Rejected It was a bug that the system property was handled outside of Stage.MODEL - where system properties like this are used they should only be used as a temporary workaround with a view to the configuration being handled in Stage.MODEL in the future. > Regression: Legacy LDAP security-realm reads system-property only during boot > ----------------------------------------------------------------------------- > > Key: WFCORE-2362 > URL: https://issues.jboss.org/browse/WFCORE-2362 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta23 > > Attachments: print-roles.war > > > In legacy LDAP security-realm, {{org.jboss.as.domain.management.security.parseGroupNameFromLdapDN}} system property is used for decision between parsing role from DN (for property=true) or LDAP role search (otherwise). LDAP security-realm was able to read this property dynamically from server configuration. Currently it seems that LDAP security-realm reads this property only during server boot. This means that if this property is set through system-property resource in application server then reload of server is needed to start this feature. > This issue does not affects scenarios, where system property is set in standalone.conf. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8809) org.jboss.as.clustering.controller.AttributeParsers.COLLECTION is redundant

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-8809: ---------------------------------- Summary: org.jboss.as.clustering.controller.AttributeParsers.COLLECTION is redundant Key: WFLY-8809 URL: https://issues.jboss.org/browse/WFLY-8809 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.Alpha1, 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro org.jboss.as.clustering.controller.AttributeParsers.COLLECTION is currently used for 2 types of attributes: * Lists * Maps The list version is unnecessary, as the default parser for the associated attribute definition parses these value correctly. The only exception is to support aliases in version 1.0 of the XSD. The map version is very hacky, as it makes an assumption that the map value is available from the element text of the xml reader. We should use a separate parser for this type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8808) AUTH fails to validate AuthHeader

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8808?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-11028 to WFLY-8808: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8808 (was: JBEAP-11028) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR11) (was: 7.1.0.DR16) (was: 7.1.0.DR17) (was: 7.1.0.DR18) > AUTH fails to validate AuthHeader > --------------------------------- > > Key: WFLY-8808 > URL: https://issues.jboss.org/browse/WFLY-8808 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > When setting up AUTH protocol and starting two servers, they fail to establish a view, because they never authenticate to each other: > Server 1: > {noformat} > 12:21:59,348 WARN [org.jgroups.protocols.AUTH] (thread-2) rjanik: failed to validate AuthHeader (token: SimpleToken) from node2; dropping message > {noformat} > Server 2: > {noformat} > 12:23:17,370 WARN [org.jgroups.protocols.AUTH] (thread-1) node2: failed to validate AuthHeader (token: SimpleToken) from node2; dropping message > 12:23:17,371 WARN [org.jgroups.protocols.AUTH] (thread-1) node2: failed to validate AuthHeader (token: SimpleToken) from node2; dropping message > 12:23:17,372 WARN [org.jgroups.protocols.AUTH] (thread-2) node2: failed to validate AuthHeader (token: SimpleToken) from rjanik; dropping message > 12:23:22,370 WARN [org.jgroups.protocols.pbcast.GMS] (MergeTask,ee,node2) node2: merge is cancelled: did not get any merge responses from partition coordinators > {noformat} > {{AUTH}} does not set up the {{auth_value}} field for the SimpleToken and MD5Token when creating them and it looks like {{setAuthToken}} is not called later. Those tokens then fail when authenticating, referencing the {{auth_value}} field. > AUTH: > {code:java} > public void setAuthClass(String class_name) throws Exception { > Object obj=Class.forName(class_name).newInstance(); > auth_token=(AuthToken)obj; > auth_token.setAuth(this); > } > {code} > MD5Token: > {code:java} > return (this.auth_value != null) && (serverToken.auth_value != null) > && (this.auth_value.equalsIgnoreCase(serverToken.auth_value)); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1568) Improve error messages when using boxed java functions

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1568: ------------------------------------- Summary: Improve error messages when using boxed java functions Key: DROOLS-1568 URL: https://issues.jboss.org/browse/DROOLS-1568 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.0.0.CR3 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final Currently, when the engine does not find the mapped java function (if the user uses an unknown java class or makes a typo in the method signature), it raises an ArrayIndexOutOfBoundsException. Fix it to properly return a meaningful message to the user, stating the java function was not found. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 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 May 2017