June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13594) Upgrade Artemis Native to 1.0.2

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-13594: ---------------------------------------- Summary: Upgrade Artemis Native to 1.0.2 Key: WFLY-13594 URL: https://issues.redhat.com/browse/WFLY-13594 Project: WildFly Issue Type: Component Upgrade Components: JMS Affects Versions: 20.0.0.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Because of a fix in the kernel, libaio is now returning duplicate events -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-5012) Upgrade Jboss Threads to 2.3.5

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFCORE-5012: -------------------------------------------- Summary: Upgrade Jboss Threads to 2.3.5 Key: WFCORE-5012 URL: https://issues.redhat.com/browse/WFCORE-5012 Project: WildFly Core Issue Type: Component Upgrade Components: Server Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana Upgrade jboss Thread to 2.3.5 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-5011) Remove licenses for artifact wildfly-jar-boot that is not in the distribution

by Roberto Oliveira (Jira)

Roberto Oliveira created WFCORE-5011: ---------------------------------------- Summary: Remove licenses for artifact wildfly-jar-boot that is not in the distribution Key: WFCORE-5011 URL: https://issues.redhat.com/browse/WFCORE-5011 Project: WildFly Core Issue Type: Bug Components: Build System Affects Versions: 13.0.0.Beta1 Reporter: Roberto Oliveira Assignee: Roberto Oliveira The artifact org.wildfly.core:wildfly-jar-boot is not in the WildFly distribution and can be excluded from the licenses -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-5147: -------------------------------------- Sprint: (was: 2020 Week 25-27 (from Jun 15)) > [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX) > -------------------------------------------------------------------------- > > Key: DROOLS-5147 > URL: https://issues.redhat.com/browse/DROOLS-5147 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Minor > Labels: UXTeam, drools-tools, kogito-tooling > Attachments: prototype.png > > > Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios: > - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field. > - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually. > The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1181) DropDown - Check open and close states first - optimize

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1181?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1181: ---------------------------------- Sprint: Kiali Sprint #41 > DropDown - Check open and close states first - optimize > ------------------------------------------------------- > > Key: SWSQE-1181 > URL: https://issues.redhat.com/browse/SWSQE-1181 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1186) Applications list test - Add back labels comparison

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1186?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan closed SWSQE-1186. --------------------------------- Resolution: Duplicate Issue > Applications list test - Add back labels comparison > --------------------------------------------------- > > Key: SWSQE-1186 > URL: https://issues.redhat.com/browse/SWSQE-1186 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > > Applications UI list comparing to OC list, labels are disabled. > Should be enabled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13589) WildFly cannot connect to an infinispan-server cluster requiring authentication

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13589?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13589: -------------------------------- Issue Type: Bug (was: Feature Request) > WildFly cannot connect to an infinispan-server cluster requiring authentication > ------------------------------------------------------------------------------- > > Key: WFLY-13589 > URL: https://issues.redhat.com/browse/WFLY-13589 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > > Infinispan 11.0 requires authentication by default. Consequently, we need the ability to configure authentication for a remote-cache-container. > See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13589) WildFly cannot connect to an infinispan-server cluster requiring authentication

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13589?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13589: -------------------------------- Summary: WildFly cannot connect to an infinispan-server cluster requiring authentication (was: Add support for configuring RHDG authentication over hotrod) > WildFly cannot connect to an infinispan-server cluster requiring authentication > ------------------------------------------------------------------------------- > > Key: WFLY-13589 > URL: https://issues.redhat.com/browse/WFLY-13589 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > > Infinispan 11.0 requires authentication by default. Consequently, we need the ability to configure authentication for a remote-cache-container. > See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1725) Remove 'org.wildfly.security.credential.source.OAuth2CredentialSource'

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/ELY-1725?page=com.atlassian.jira.plugin.... ] Ashley Abdel-Sayed commented on ELY-1725: ----------------------------------------- [~noelvaes] ELY-1724 would copy the {{org.wildfly.security.credential.source.OAuth2CredentialSource}} from the authentication client module to the credential source module. > Remove 'org.wildfly.security.credential.source.OAuth2CredentialSource' > ---------------------------------------------------------------------- > > Key: ELY-1725 > URL: https://issues.redhat.com/browse/ELY-1725 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 2.0.0.Alpha8 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-5004) TlsTestCase#testReloadTrustManager fails on IBM Java 8

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFCORE-5004?page=com.atlassian.jira.plug... ] Sonia Zaldana commented on WFCORE-5004: --------------------------------------- When the X500Principal is extracted from the X509Certificate, it contains the email address in encoded form in the canonical representation, so we need to use getName() instead which will use the RFC 2253 representation. > TlsTestCase#testReloadTrustManager fails on IBM Java 8 > ------------------------------------------------------ > > Key: WFCORE-5004 > URL: https://issues.redhat.com/browse/WFCORE-5004 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta1 > Reporter: Ondrej Kotek > Assignee: Sonia Zaldana > Priority: Major > > TlsTestCase#testReloadTrustManager fails on IBM Java 8 at [TlsTestCase.java#L439|https://github.com/wildfly/wildfly-core/blob/master...] reporting the same DN. When I try to compare using canonical names, there is a difference. Using RFC1779 or RFC2253 names is ok. > {noformat} > Assert.assertEquals(originalFoundDN.getIssuerX500Principal().getName(X500Principal.CANONICAL), ISSUER_DN.getName(X500Principal.CANONICAL)); > [ERROR] TlsTestCase.testReloadTrustManager:439 expected:<....2.840.113549.1.9.1=[#1613656c7974726f6e4077696c64666c792e6f7267],c=uk,st=elytron,cn=...> but was:<....2.840.113549.1.9.1=[elytron@wildfly.org],c=uk,st=elytron,cn=...> > {noformat} > Is it just a test issue, or can there be an impact on functionality? In case it's just a test issue, can we assert equality of names? I.e. > {noformat} > Assert.assertEquals(originalFoundDN.getIssuerX500Principal().getName(), ISSUER_DN.getName()); > {noformat} > The same for [TlsTestCase.java#L465|https://github.com/wildfly/wildfly-core/blob/master...] then. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 June 2020