September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1663) BC FIPS, Solaris 11 sparc ELY04001: No algorithm found matching TLS/SSL protocol selection criteria

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1663?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1663: ----------------------------------- Now test pass on all platforms also on solaris 11 sparc . I will keep this issue open in case it is some race condition in server code. Once ELY-1664 will get into WF I will monitor the results if we can get more info and isolate the cause. Note, there is still chance it is enviroment issue or testsuite issue. > BC FIPS, Solaris 11 sparc ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > --------------------------------------------------------------------------------------------------- > > Key: ELY-1663 > URL: https://issues.jboss.org/browse/ELY-1663 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.6.0.Final > Reporter: Martin Choma > Priority: Critical > > On Solaris 11 sparc http management interface secured with TLS fails with BC FIPS > {code} > Operation {"operation" => "add","address" => [("subsystem" => "elytron"),("server-ssl-context" => "test-server-ssl-context")],"key-manager" => "key-manager-name_test-server-ssl-context","cipher-suite-filter" => "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256","trust-manager" => "trust-manager-name_test-server-ssl-context","protocols" => ["TLSv1.2"],"need-client-auth" => true} failed: {"outcome" => "failed","failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.test-server-ssl-context" => "java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria"}},"rolled-back" => true} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.security.ssl-context.test-server-ssl-context: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.test-server-ssl-context: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:982) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > at org.wildfly.security.ssl.SSLUtils.lambda$createSslContextFactory$1(SSLUtils.java:130) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:340) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:980) > ... 9 more > {code} > Some facts > * It happends only on BC FIPS management interface TLS tests and on Solaris 11 sparc > * BC FIPS Management interface TLS tests work on all other tested platforms > * TLSv1.2 protocol works with Undertow on Solaris 11 sparc > * Previously there was issue with similar error but that happened everywhere https://issues.jboss.org/browse/ELY-1618 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11004) The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-11004?page=com.atlassian.jira.plugin... ] Jan Kašík moved JBEAP-15415 to WFLY-11004: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11004 (was: JBEAP-15415) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JSF (was: JSF) Affects Version/s: 15.0.0.Alpha1 (was: 7.1.0.DR16) Fix Version/s: (was: 7.1.2.GA) (was: 7.1.2.CR1) > The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11004 > URL: https://issues.jboss.org/browse/WFLY-11004 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 15.0.0.Alpha1 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > > When setting {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} to true, the old (or initial) model value is redisplayed on {{@NotNull}} validation error instead of the submitted value. > A required submitted value, which is afterwards removed and re-submitted, should not reappear. > This issue is reported in [JAVASERVERFACES_SPEC_PUBLIC-671|https://java.net/jira/browse/JAVASERVERFA...] and it's fixed in [the revision 0813ee1fdef418e47ef03ced7d57a1abe4c2bf54|https://github.com/javaserverfac...]. Please backport this to JBoss mojarra. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11004) The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-11004?page=com.atlassian.jira.plugin... ] Jan Kašík reassigned WFLY-11004: -------------------------------- Assignee: Farah Juma (was: Dmitrii Tikhomirov) > The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11004 > URL: https://issues.jboss.org/browse/WFLY-11004 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 15.0.0.Alpha1 > Reporter: Jan Kašík > Assignee: Farah Juma > > When setting {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} to true, the old (or initial) model value is redisplayed on {{@NotNull}} validation error instead of the submitted value. > A required submitted value, which is afterwards removed and re-submitted, should not reappear. > This issue is reported in [JAVASERVERFACES_SPEC_PUBLIC-671|https://java.net/jira/browse/JAVASERVERFA...] and it's fixed in [the revision 0813ee1fdef418e47ef03ced7d57a1abe4c2bf54|https://github.com/javaserverfac...]. Please backport this to JBoss mojarra. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10741) Relicense Quickstarts and BOMs as Apache 2.0

by Vladimir Dosoudil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10741?page=com.atlassian.jira.plugin... ] Vladimir Dosoudil commented on WFLY-10741: ------------------------------------------ MUST HAVE: license tag in root pom.xml SHOULD HAVE: LICENSE.txt file in the root folder CAN HAVE: license specified/described in README file > Relicense Quickstarts and BOMs as Apache 2.0 > -------------------------------------------- > > Key: WFLY-10741 > URL: https://issues.jboss.org/browse/WFLY-10741 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Reporter: Kabir Khan > Assignee: Eduardo Martins > > There has been a bit back and forth on the bom and QS licenses in WF12, 13 and 14. For WF15, we should relicense them all (where possible) to Apache 2.0. > Note that we will need: > A LICENCE.txt in the root folder > The name of the license in the BOMs should be from the 'Full Name' column of https://spdx.org/licenses/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2820) [DMN Designer] [IE11] Node deletion throws an Error

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2820?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2820: -------------------------------- Description: After node deletion error dialo appears: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?* h2. Manual Acceptance test - Select in decision navigator dock, delete by `delete` key - Select in decision navigator dock, delete by toolbox trash icon - Select in decision navigator dock, delete by context trash icon - Select on canvas, delete by `delete` key - Select on canvas, delete by toolbox trash icon - Select on canvas, delete by context trash icon was:After node deletion error dialo appears: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?* > [DMN Designer] [IE11] Node deletion throws an Error > --------------------------------------------------- > > Key: DROOLS-2820 > URL: https://issues.jboss.org/browse/DROOLS-2820 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Environment: IE11 > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Labels: drools-tools > > After node deletion error dialo appears: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?* > h2. Manual Acceptance test > - Select in decision navigator dock, delete by `delete` key > - Select in decision navigator dock, delete by toolbox trash icon > - Select in decision navigator dock, delete by context trash icon > - Select on canvas, delete by `delete` key > - Select on canvas, delete by toolbox trash icon > - Select on canvas, delete by context trash icon -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11000) Upgrade dom4j from 1.6.1 to 2.1.1

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-11000?page=com.atlassian.jira.plugin... ] Chao Wang updated WFLY-11000: ----------------------------- Security Sensitive Issue: This issue is security relevant > Upgrade dom4j from 1.6.1 to 2.1.1 > --------------------------------- > > Key: WFLY-11000 > URL: https://issues.jboss.org/browse/WFLY-11000 > Project: WildFly > Issue Type: Component Upgrade > Affects Versions: 14.0.0.Final > Reporter: Chao Wang > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4107) Upgrade MSC to 1.4.5.Final

by Richard Opalka (JIRA)

Richard Opalka created WFCORE-4107: -------------------------------------- Summary: Upgrade MSC to 1.4.5.Final Key: WFCORE-4107 URL: https://issues.jboss.org/browse/WFCORE-4107 Project: WildFly Core Issue Type: Component Upgrade Components: Management, Server Affects Versions: 6.0.2.Final Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4106) Add the ability to configure security providers using Elytron subsystem security properties

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4106?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFCORE-4106: ------------------------------------ Analysis document: https://github.com/wildfly/wildfly-proposals/pull/128 > Add the ability to configure security providers using Elytron subsystem security properties > ------------------------------------------------------------------------------------------- > > Key: WFCORE-4106 > URL: https://issues.jboss.org/browse/WFCORE-4106 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > > It should be possible to configure security providers using the {{security-properties}} attribute in the Elytron subsystem. For example, it should be possible to use the following command to register custom security providers instead of needing to manually update the {{java.security}} file: > {code} > /subsystem=elytron:write-attribute(name=security-properties,value={\ > security.provider.1=PROVIDER_1,\ > security.provider.2=PROVIDER_2\ > ...\ > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-414) Integrate Maistra-Productized-Job on Pipeline

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-414: --------------------------------------------- Summary: Integrate Maistra-Productized-Job on Pipeline Key: SWSQE-414 URL: https://issues.jboss.org/browse/SWSQE-414 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-414) Integrate Maistra-Productized-Job on Pipeline

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-414?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-414: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Integrate Maistra-Productized-Job on Pipeline > --------------------------------------------- > > Key: SWSQE-414 > URL: https://issues.jboss.org/browse/SWSQE-414 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 September 2018