[JBoss JIRA] (WFCORE-4127) Disable CLI paging with an option
by Marek Marusic (JIRA)
Marek Marusic created WFCORE-4127:
-------------------------------------
Summary: Disable CLI paging with an option
Key: WFCORE-4127
URL: https://issues.jboss.org/browse/WFCORE-4127
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Marek Marusic
Assignee: Marek Marusic
In some cases, for example, copy/pasting of the full output is required. The paging could be disabled by a simple option.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, 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 edited comment on ELY-1663 at 9/25/18 8:42 AM:
------------------------------------------------------------
Thanks to ELY-1664 I now see
{code:title=NOK}
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLS
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.1
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.2
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm DEFAULT
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLS
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.2
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLS
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1.1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1.2
08:01:49,728 TRACE [org.wildfly.security] (MSC service thread 1-1) Supported protocols are: [TLSv1.2]
08:01:49,795 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 has no such protocol TLSv1.2
08:01:49,796 TRACE [org.wildfly.security] (MSC service thread 1-1) No SSLContext provided by providers in SSLUtils: [BCFIPS version 1.01, BCJSSE version 1.0005, SUN version 1.8, ApacheXMLDSig version 2.12, SunJCE version 1.8, WildFlyElytron version 1.0, TLSP version 1.0, openssl version 1.0]
08:01:49,797 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) 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:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
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:151)
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}
{code:title=OK}
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm DEFAULT
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Supported protocols are: [TLSV1.2]
[0m07:47:38,426 TRACE [org.wildfly.security.tls] (MSC service thread 1-3) SSLContext initialization:
securityDomain = null
canAuthPeers = false
cipherSuiteSelector = add cipher name is "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_DHE_DSS_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_256_CBC_SHA256", then add cipher name is "TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384", then add cipher name is "TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_RSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_RSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_256_CBC_SHA256"
protocolSelector = add protocols (TLSv1_2)
x509TrustManager = org.bouncycastle.jsse.provider.ProvX509ExtendedTrustManager_7@5cf78cec
x509KeyManager = org.wildfly.extension.elytron.SSLDefinitions$DelegatingKeyManager@3840d33b
providerSupplier = org.wildfly.security.util.ProviderUtil$$Lambda$378/1963271128@52af0c28
clientMode = false
authenticationOptional = false
sessionCacheSize = -1
sessionTimeout = -1
wantClientAuth = false
needClientAuth = false
useCipherSuitesOrder = true
wrap = false
{code}
was (Author: mchoma):
Thanks to ELY-1664 I now see
{code:title=OK}
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLS
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.1
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.2
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm DEFAULT
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLS
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.2
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLS
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1.1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1.2
08:01:49,728 TRACE [org.wildfly.security] (MSC service thread 1-1) Supported protocols are: [TLSv1.2]
08:01:49,795 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 has no such protocol TLSv1.2
08:01:49,796 TRACE [org.wildfly.security] (MSC service thread 1-1) No SSLContext provided by providers in SSLUtils: [BCFIPS version 1.01, BCJSSE version 1.0005, SUN version 1.8, ApacheXMLDSig version 2.12, SunJCE version 1.8, WildFlyElytron version 1.0, TLSP version 1.0, openssl version 1.0]
08:01:49,797 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) 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:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
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:151)
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}
{code:title=NOK}
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm DEFAULT
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Supported protocols are: [TLSV1.2]
[0m07:47:38,426 TRACE [org.wildfly.security.tls] (MSC service thread 1-3) SSLContext initialization:
securityDomain = null
canAuthPeers = false
cipherSuiteSelector = add cipher name is "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_DHE_DSS_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_256_CBC_SHA256", then add cipher name is "TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384", then add cipher name is "TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_RSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_RSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_256_CBC_SHA256"
protocolSelector = add protocols (TLSv1_2)
x509TrustManager = org.bouncycastle.jsse.provider.ProvX509ExtendedTrustManager_7@5cf78cec
x509KeyManager = org.wildfly.extension.elytron.SSLDefinitions$DelegatingKeyManager@3840d33b
providerSupplier = org.wildfly.security.util.ProviderUtil$$Lambda$378/1963271128@52af0c28
clientMode = false
authenticationOptional = false
sessionCacheSize = -1
sessionTimeout = -1
wantClientAuth = false
needClientAuth = false
useCipherSuitesOrder = true
wrap = false
{code}
> 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
> Priority: Critical
>
> 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.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-11067) Use DynamicNameMappers global name mappers instead of lambdas
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFLY-11067:
----------------------------------------
Summary: Use DynamicNameMappers global name mappers instead of lambdas
Key: WFLY-11067
URL: https://issues.jboss.org/browse/WFLY-11067
Project: WildFly
Issue Type: Enhancement
Components: JMS, Mail, Web (Undertow)
Affects Versions: 14.0.0.Final
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Priority: Minor
With the new DynamicNameMappers class in core we can remove some lambdas from full
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, 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:
-----------------------------------
Thanks to ELY-1664 I now see
{code:title=OK}
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLS
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.1
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.2
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm DEFAULT
08:01:49,725 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider BCJSSE version 1.0005 was added for algorithm TLSV1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLS
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.2
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLS
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1.1
08:01:49,726 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 was added for algorithm TLSv1.2
08:01:49,728 TRACE [org.wildfly.security] (MSC service thread 1-1) Supported protocols are: [TLSv1.2]
08:01:49,795 TRACE [org.wildfly.security] (MSC service thread 1-1) Provider openssl version 1.0 has no such protocol TLSv1.2
08:01:49,796 TRACE [org.wildfly.security] (MSC service thread 1-1) No SSLContext provided by providers in SSLUtils: [BCFIPS version 1.01, BCJSSE version 1.0005, SUN version 1.8, ApacheXMLDSig version 2.12, SunJCE version 1.8, WildFlyElytron version 1.0, TLSP version 1.0, openssl version 1.0]
08:01:49,797 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) 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:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
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:151)
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}
{code:title=NOK}
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm DEFAULT
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider BCJSSE version 1.0005 was added for algorithm TLSV1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm openssl.TLSv1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLS
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1.1
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Provider openssl version 1.0 was added for algorithm TLSv1.2
[0m07:47:38,425 TRACE [org.wildfly.security] (MSC service thread 1-3) Supported protocols are: [TLSV1.2]
[0m07:47:38,426 TRACE [org.wildfly.security.tls] (MSC service thread 1-3) SSLContext initialization:
securityDomain = null
canAuthPeers = false
cipherSuiteSelector = add cipher name is "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_DHE_DSS_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_DHE_DSS_WITH_AES_256_CBC_SHA256", then add cipher name is "TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384", then add cipher name is "TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_RSA_WITH_3DES_EDE_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_128_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_128_CBC_SHA256", then add cipher name is "TLS_RSA_WITH_AES_256_CBC_SHA", then add cipher name is "TLS_RSA_WITH_AES_256_CBC_SHA256"
protocolSelector = add protocols (TLSv1_2)
x509TrustManager = org.bouncycastle.jsse.provider.ProvX509ExtendedTrustManager_7@5cf78cec
x509KeyManager = org.wildfly.extension.elytron.SSLDefinitions$DelegatingKeyManager@3840d33b
providerSupplier = org.wildfly.security.util.ProviderUtil$$Lambda$378/1963271128@52af0c28
clientMode = false
authenticationOptional = false
sessionCacheSize = -1
sessionTimeout = -1
wantClientAuth = false
needClientAuth = false
useCipherSuitesOrder = true
wrap = false
{code}
> 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
> Priority: Critical
>
> 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.5.0#75005)
7 years, 8 months
[JBoss JIRA] (SWSQE-421) Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
by Lucas Ponce (JIRA)
[ https://issues.jboss.org/browse/SWSQE-421?page=com.atlassian.jira.plugin.... ]
Lucas Ponce updated SWSQE-421:
------------------------------
Attachment: bookinfo-123-mix.yaml
bookinfo-123-pod.yaml
bookinfo-123-daemonset.yaml
bookinfo-123-deploymentconfig.yaml
bookinfo-123-statefulset.yaml
bookinfo-123-replicaset.yaml
bookinfo-123-replicationcontroller.yaml
> Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
> -----------------------------------------------------------------------
>
> Key: SWSQE-421
> URL: https://issues.jboss.org/browse/SWSQE-421
> Project: Kiali QE
> Issue Type: Dev Task
> Reporter: Lucas Ponce
> Assignee: Guilherme Baufaker Rêgo
> Attachments: bookinfo-123-daemonset.yaml, bookinfo-123-deploymentconfig.yaml, bookinfo-123-mix.yaml, bookinfo-123-pod.yaml, bookinfo-123-replicaset.yaml, bookinfo-123-replicationcontroller.yaml, bookinfo-123-statefulset.yaml
>
>
> Related to KIALI-1284, Kiali will support several types for deployments.
> Currently, only Deployment objects are fully supported on list pages.
> Also, to sync with the current OpenShift Web Console, we plan to support: Deployment, ReplicaSet, ReplicationController and DeploymentConfig (this one is not a kubernetes object, but only OpenShift one).
> So, in order to help in the testing, Kiali Test Mesh could add these new types: ReplicationController and DeploymentConfig to deploy a test scenario that we can use for our testing.
> I.e.
> {code}
> DEPLOYMENT_TYPE=ReplicationController NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> DEPLOYMENT_TYPE=DeploymentConfig NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (SWSQE-421) Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
by Lucas Ponce (JIRA)
[ https://issues.jboss.org/browse/SWSQE-421?page=com.atlassian.jira.plugin.... ]
Lucas Ponce commented on SWSQE-421:
-----------------------------------
bookinfo-123-mix.yaml is a combined scenario where Pods can be created from multiple controllers.
> Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
> -----------------------------------------------------------------------
>
> Key: SWSQE-421
> URL: https://issues.jboss.org/browse/SWSQE-421
> Project: Kiali QE
> Issue Type: Dev Task
> Reporter: Lucas Ponce
> Assignee: Guilherme Baufaker Rêgo
> Attachments: bookinfo-123-daemonset.yaml, bookinfo-123-deploymentconfig.yaml, bookinfo-123-mix.yaml, bookinfo-123-pod.yaml, bookinfo-123-replicaset.yaml, bookinfo-123-replicationcontroller.yaml, bookinfo-123-statefulset.yaml
>
>
> Related to KIALI-1284, Kiali will support several types for deployments.
> Currently, only Deployment objects are fully supported on list pages.
> Also, to sync with the current OpenShift Web Console, we plan to support: Deployment, ReplicaSet, ReplicationController and DeploymentConfig (this one is not a kubernetes object, but only OpenShift one).
> So, in order to help in the testing, Kiali Test Mesh could add these new types: ReplicationController and DeploymentConfig to deploy a test scenario that we can use for our testing.
> I.e.
> {code}
> DEPLOYMENT_TYPE=ReplicationController NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> DEPLOYMENT_TYPE=DeploymentConfig NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (SWSQE-421) Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
by Lucas Ponce (JIRA)
[ https://issues.jboss.org/browse/SWSQE-421?page=com.atlassian.jira.plugin.... ]
Lucas Ponce commented on SWSQE-421:
-----------------------------------
I am using a file for local testing that can help to validate the scenarios we can cover.
I attach it to the JIRA.
> Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
> -----------------------------------------------------------------------
>
> Key: SWSQE-421
> URL: https://issues.jboss.org/browse/SWSQE-421
> Project: Kiali QE
> Issue Type: Dev Task
> Reporter: Lucas Ponce
> Assignee: Guilherme Baufaker Rêgo
>
> Related to KIALI-1284, Kiali will support several types for deployments.
> Currently, only Deployment objects are fully supported on list pages.
> Also, to sync with the current OpenShift Web Console, we plan to support: Deployment, ReplicaSet, ReplicationController and DeploymentConfig (this one is not a kubernetes object, but only OpenShift one).
> So, in order to help in the testing, Kiali Test Mesh could add these new types: ReplicationController and DeploymentConfig to deploy a test scenario that we can use for our testing.
> I.e.
> {code}
> DEPLOYMENT_TYPE=ReplicationController NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> DEPLOYMENT_TYPE=DeploymentConfig NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (SWSQE-421) Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-421?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo commented on SWSQE-421:
-----------------------------------------------
[~hhovsepy] [~rutlucas] Starting today.
> Kiali Test Mesh support for ReplicationControllers and DeploymentConfig
> -----------------------------------------------------------------------
>
> Key: SWSQE-421
> URL: https://issues.jboss.org/browse/SWSQE-421
> Project: Kiali QE
> Issue Type: Dev Task
> Reporter: Lucas Ponce
> Assignee: Guilherme Baufaker Rêgo
>
> Related to KIALI-1284, Kiali will support several types for deployments.
> Currently, only Deployment objects are fully supported on list pages.
> Also, to sync with the current OpenShift Web Console, we plan to support: Deployment, ReplicaSet, ReplicationController and DeploymentConfig (this one is not a kubernetes object, but only OpenShift one).
> So, in order to help in the testing, Kiali Test Mesh could add these new types: ReplicationController and DeploymentConfig to deploy a test scenario that we can use for our testing.
> I.e.
> {code}
> DEPLOYMENT_TYPE=ReplicationController NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> DEPLOYMENT_TYPE=DeploymentConfig NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (SWSQE-419) Enhance Maistra Pipeline Support
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-419?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo resolved SWSQE-419.
-------------------------------------------
Resolution: Done
> Enhance Maistra Pipeline Support
> --------------------------------
>
> Key: SWSQE-419
> URL: https://issues.jboss.org/browse/SWSQE-419
> Project: Kiali QE
> Issue Type: Story
> Reporter: Guilherme Baufaker Rêgo
> Assignee: Guilherme Baufaker Rêgo
>
> Maistra Pipeline would need to have some additions to have better support (Some of them include)
> - Remove Maistra Job from Upstream Pipeline (SWSQE-423)
> - Add Minimal CR option (this will install default versions listed on istio-operator) - (SWSQE-429)
>
> - Include Option to run or not run Kiali Istio Checker
>
> - Crate Maistra Message Bus Job (SWSQE-424)
> - Include Bookinfo, Include E2E Test Run, Include UI Test Run (SWSQE-430)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months