[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELY-1663?page=com.atlassian.jira.plugin.s... ]
Farah Juma updated ELY-1663:
----------------------------
Priority: Major (was: Blocker)
> BC FIPS, Management Interface, 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
> Assignee: Farah Juma
> Priority: Major
>
> Rarely 1:30 it happens there occures error accessing http management interface secured with TLS 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 happens only on management interface BC FIPS TLS tests
> * It does not occur on Undertow secured with BC FIPS
> * 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.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELY-1663?page=com.atlassian.jira.plugin.s... ]
Farah Juma commented on ELY-1663:
---------------------------------
Lowered the priority of this issue as discussed with Martin.
> BC FIPS, Management Interface, 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
> Assignee: Farah Juma
> Priority: Major
>
> Rarely 1:30 it happens there occures error accessing http management interface secured with TLS 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 happens only on management interface BC FIPS TLS tests
> * It does not occur on Undertow secured with BC FIPS
> * 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.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3288?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3288:
---------------------------------------
Description:
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
..and change the Input Node type, the type in the Decision Table does not change.
*Steps to reproduce*
!steps.gif|thumbnail!
*Expected behaviour*
Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
was:
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
..and change the Input Node type, the type in the Decision Table does not change.
*Steps to reproduce*
!steps.gif|thumbnail!
*Expected behaviour*
Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
> [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
> ----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3288
> URL: https://issues.jboss.org/browse/DROOLS-3288
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: diagram.png, dtable.png, steps.gif
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..and change the Input Node type, the type in the Decision Table does not change.
> *Steps to reproduce*
> !steps.gif|thumbnail!
> *Expected behaviour*
> Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3288?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3288:
---------------------------------------
Description:
*Description*
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
..and change the Input Node type, the type in the Decision Table does not change.
*Steps to reproduce*
!steps.gif|thumbnail!
*Expected behaviour*
Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
was:
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
..and change the Input Node type, the type in the Decision Table does not change.
See the steps to reproduce:
!steps.gif|thumbnail!
Ideally, these types should be synchronised, however since one is persisted as a `dmn:inputExpression` (type in the DT column) and the other as a `dmn:variable`, the user should be able to re-define the types, keeping them unsynchronised.
> [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
> ----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3288
> URL: https://issues.jboss.org/browse/DROOLS-3288
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: diagram.png, dtable.png, steps.gif
>
>
> *Description*
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..and change the Input Node type, the type in the Decision Table does not change.
> *Steps to reproduce*
> !steps.gif|thumbnail!
> *Expected behaviour*
> Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3288?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3288:
---------------------------------------
Description:
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
..and change the Input Node type, the type in the Decision Table does not change.
*Steps to reproduce*
!steps.gif|thumbnail!
*Expected behaviour*
Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
was:
*Description*
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
..and change the Input Node type, the type in the Decision Table does not change.
*Steps to reproduce*
!steps.gif|thumbnail!
*Expected behaviour*
Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
> [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
> ----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3288
> URL: https://issues.jboss.org/browse/DROOLS-3288
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: diagram.png, dtable.png, steps.gif
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..and change the Input Node type, the type in the Decision Table does not change.
> *Steps to reproduce*
> !steps.gif|thumbnail!
> *Expected behaviour*
> Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3288?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-3288 at 11/8/18 1:49 PM:
---------------------------------------------------------------------
[~tirelli],
I'd like to clarify the requirement for this JIRA. Let me expose the synchronisation workflow:
- If the user changes the type of an Input Node, the change should reflect in the Decision Table column;
- If the user changes the type in the Decision Table column, nothing happens.
Are these assumptions right?
Thanks.
was (Author: karreiro):
[~tirelli],
I'd like to clarify the requirement for this JIRA. Let me expose the synchronisation workflow:
- If the user changes the type of an Input Node, the change should reflect in the Decision Table column;
- If the user changes the type in the Decision Table column, nothing happens.
Am I right?
Thanks.
> [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
> ----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3288
> URL: https://issues.jboss.org/browse/DROOLS-3288
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: diagram.png, dtable.png, steps.gif
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..and change the Input Node type, the type in the Decision Table does not change.
> See the steps to reproduce:
> !steps.gif|thumbnail!
> Ideally, these types should be synchronised, however since one is persisted as a `dmn:inputExpression` (type in the DT column) and the other as a `dmn:variable`, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3288?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-3288:
--------------------------------------------
[~tirelli],
I'd like to clarify the requirement for this JIRA. Let me expose the synchronisation workflow:
- If the user changes the type of an Input Node, the change should reflect in the Decision Table column;
- If the user changes the type in the Decision Table column, nothing happens.
Am I right?
Thanks.
> [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
> ----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3288
> URL: https://issues.jboss.org/browse/DROOLS-3288
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: diagram.png, dtable.png, steps.gif
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..and change the Input Node type, the type in the Decision Table does not change.
> See the steps to reproduce:
> !steps.gif|thumbnail!
> Ideally, these types should be synchronised, however since one is persisted as a `dmn:inputExpression` (type in the DT column) and the other as a `dmn:variable`, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3288?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3288:
---------------------------------------
Tester: Jozef Marko
> [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
> ----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3288
> URL: https://issues.jboss.org/browse/DROOLS-3288
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: diagram.png, dtable.png, steps.gif
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..and change the Input Node type, the type in the Decision Table does not change.
> See the steps to reproduce:
> !steps.gif|thumbnail!
> Ideally, these types should be synchronised, however since one is persisted as a `dmn:inputExpression` (type in the DT column) and the other as a `dmn:variable`, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3288:
------------------------------------------
Summary: [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
Key: DROOLS-3288
URL: https://issues.jboss.org/browse/DROOLS-3288
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Michael Anstis
Attachments: diagram.png, dtable.png, steps.gif
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
..and change the Input Node type, the type in the Decision Table does not change.
See the steps to reproduce:
!steps.gif|thumbnail!
Ideally, these types should be synchronised, however since one is persisted as a `dmn:inputExpression` (type in the DT column) and the other as a `dmn:variable`, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months