August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10819) Adjust provisioning configs to reduce configuration diff noise

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-10819?page=com.atlassian.jira.plugin... ] Alexey Loubyansky moved WFCORE-4012 to WFLY-10819: -------------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-10819 (was: WFCORE-4012) Component/s: Build System (was: Build System) > Adjust provisioning configs to reduce configuration diff noise > -------------------------------------------------------------- > > Key: WFLY-10819 > URL: https://issues.jboss.org/browse/WFLY-10819 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > This is a minor issue in a sense it can be viewed as cosmetic changes in provisioning configs. Its priority however will get higher once we start generating configuration diffs during provisioning. > The issue is that if build the default distribution today and compare it to itself, there will appear some differences in the configs. Those differences are not actual differences but simply noise. It is caused by the fact there are sometimes multiple ways to express the same configuration. > Applying the changes linked to this issue will avoid the diff noise and comparing the default distribution to itself won't produce any config diff. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10819) Adjust provisioning configs to reduce configuration diff noise

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-10819?page=com.atlassian.jira.plugin... ] Alexey Loubyansky updated WFLY-10819: ------------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3431) > Adjust provisioning configs to reduce configuration diff noise > -------------------------------------------------------------- > > Key: WFLY-10819 > URL: https://issues.jboss.org/browse/WFLY-10819 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > This is a minor issue in a sense it can be viewed as cosmetic changes in provisioning configs. Its priority however will get higher once we start generating configuration diffs during provisioning. > The issue is that if build the default distribution today and compare it to itself, there will appear some differences in the configs. Those differences are not actual differences but simply noise. It is caused by the fact there are sometimes multiple ways to express the same configuration. > Applying the changes linked to this issue will avoid the diff noise and comparing the default distribution to itself won't produce any config diff. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1618) TLS with BCJSSE Provider does not work

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1618?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1618: ---------------------------------- Fix Version/s: 1.5.2.CR1 > TLS with BCJSSE Provider does not work > -------------------------------------- > > Key: ELY-1618 > URL: https://issues.jboss.org/browse/ELY-1618 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.4.0.Final > Reporter: Martin Choma > Assignee: Farah Juma > Priority: Blocker > Fix For: 1.5.1.Final, 1.5.2.CR1 > > Attachments: standalone.v29.xml > > > When I configure BouncyCastleJsseProvider to by only possible provider providing TLS TLS does not work with exception > {code} > 14:07:53,905 TRACE [org.wildfly.security] (MSC service thread 1-4) No SSLContext provided by providers in SSLUtils: [BCFIPS version 1.01, BCJSSE version 1.0005, SUN version 1.8, ApacheXMLDSig version 2.11, SunJCE version 1.8, TLSP version 1.0, WildFlyElytron version 1.0] > 14:07:53,906 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) 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:926) > 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.throwIt(SSLUtils.java:142) > 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:924) > ... 9 more > 14:07:53,910 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("server-ssl-context" => "test-server-ssl-context") > ]) - 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"}} > {code} > After debugging it seems problem is this: > Supported protocols resolved from BCJSSE version 1.0005 are [TLS, TLSV1, TLSV1.2, DEFAULT, TLSV1.1] > Whereas Elytron class org.wildfly.security.ssl.Protocol use constants TLSv1, TLSv1.1, TLSv1.2, ... It means lower case "v" > And thus ProtocolSelector.evaluate does return empty set. > Possible solution to this particular problem will be make Protocol case insensitive. It means define enum constants in upper case and adjust methods to use .toUpperCase(). But I am probably not aware of all consequences of such change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1628) Release WildFly Elytron 1.5.2.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1628?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1628. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.5.2.Final > ----------------------------------- > > Key: ELY-1628 > URL: https://issues.jboss.org/browse/ELY-1628 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.5.2.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4012) Adjust provisioning configs to reduce configuration diff noise

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-4012: ----------------------------------------- Summary: Adjust provisioning configs to reduce configuration diff noise Key: WFCORE-4012 URL: https://issues.jboss.org/browse/WFCORE-4012 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky This is a minor issue in a sense it can be viewed as cosmetic changes in provisioning configs. Its priority however will get higher once we start generating configuration diffs during provisioning. The issue is that if build the default distribution today and compare it to itself, there will appear some differences in the configs. Those differences are not actual differences but simply noise. It is caused by the fact there are sometimes multiple ways to express the same configuration. Applying the changes linked to this issue will avoid the diff noise and comparing the default distribution to itself won't produce any config diff. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4010) Adjust provisioning configs to reduce configuration diff noise

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-4010: ----------------------------------------- Summary: Adjust provisioning configs to reduce configuration diff noise Key: WFCORE-4010 URL: https://issues.jboss.org/browse/WFCORE-4010 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky This is a minor issue in a sense it can be viewed as cosmetic changes in provisioning configs. Its priority however will get higher once we start generating configuration diffs during provisioning. The issue is that if build the default distribution today and compare it to itself, there will appear some differences in the configs. Those differences are not actual differences but simply noise. It is caused by the fact there are sometimes multiple ways to express the same configuration. Applying the changes linked to this issue will avoid the diff noise and comparing the default distribution to itself won't produce any config diff. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4011) Upgrade WildFly Elytron to 1.5.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4011: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.5.2.Final Key: WFCORE-4011 URL: https://issues.jboss.org/browse/WFCORE-4011 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 6.0.0.Alpha6 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1628) Release WildFly Elytron 1.5.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1628: ------------------------------------- Summary: Release WildFly Elytron 1.5.2.Final Key: ELY-1628 URL: https://issues.jboss.org/browse/ELY-1628 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.5.2.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3991) read-config-as-features management operation

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3991?page=com.atlassian.jira.plugi... ] Alexey Loubyansky updated WFCORE-3991: -------------------------------------- Summary: read-config-as-features management operation (was: read-provisioning-config management operation) > read-config-as-features management operation > -------------------------------------------- > > Key: WFCORE-3991 > URL: https://issues.jboss.org/browse/WFCORE-3991 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Server > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > Currently we have read-feature-description management operation which returns descriptions of available provisioning features, which is the basis for Galleon feature spec generation. > I would like to add another operation that will describe the current state of the management model in terms of provisioning features (for both standalone and domain modes). The result of this operation will be used to identify user configuration changes since the last provisioned state, which will have to be done for basically any provisioning operation (such as applying patches, installing updates, etc). > I would like to have it in EAP 7.2 even if Galleon patching is postponed to a 7.3. This feature will still allow us to upgrade from 7.2 to 7.3. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10818) Exclude org.wildfly transitive dependencies from the wildfly server feature pack used by the clustering tests

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-10818?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-10818: -------------------------------- Summary: Exclude org.wildfly transitive dependencies from the wildfly server feature pack used by the clustering tests (was: Exclude org.wildfly transitive dependencies of wildfly server used by clustering tests) > Exclude org.wildfly transitive dependencies from the wildfly server feature pack used by the clustering tests > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10818 > URL: https://issues.jboss.org/browse/WFLY-10818 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Yeray Borges > Assignee: Yeray Borges > > The transitive dependencies brought in to the test scope by the infinispan server used in clustering module should be excluded because they can pollute the test classpath if the project groupid changes from org.wildfly to something different. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 2018