August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ] Martin Choma updated ELY-1639: ------------------------------ Attachment: wildfly-config.xml > FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used > ------------------------------------------------------------- > > Key: ELY-1639 > URL: https://issues.jboss.org/browse/ELY-1639 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Martin Choma > Assignee: Farah Juma > Priority: Blocker > > Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception > {code} > 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost' > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) > ... 5 more > Caused by: java.io.IOException: Failed to obtain SSLContext > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156) > at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222) > ... 8 more > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208) > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153) > ... 10 more > {code} > It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ] Martin Choma updated ELY-1639: ------------------------------ Attachment: (was: wildfly-config.xml) > FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used > ------------------------------------------------------------- > > Key: ELY-1639 > URL: https://issues.jboss.org/browse/ELY-1639 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Martin Choma > Assignee: Farah Juma > Priority: Blocker > > Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception > {code} > 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost' > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) > ... 5 more > Caused by: java.io.IOException: Failed to obtain SSLContext > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156) > at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222) > ... 8 more > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208) > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153) > ... 10 more > {code} > It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on WFWIP-90: ------------------------------------- Ok, I've took your branch and Martyn's WF integration and started job: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10834) Load provider settings is not taken into account in mod_cluster subsystem

by Jan Kašík (JIRA)

Jan Kašík created WFLY-10834: -------------------------------- Summary: Load provider settings is not taken into account in mod_cluster subsystem Key: WFLY-10834 URL: https://issues.jboss.org/browse/WFLY-10834 Project: WildFly Issue Type: Bug Components: mod_cluster Affects Versions: 14.0.0.CR1 Environment: Latest nightly from ci.wildfly.org Reporter: Jan Kašík Assignee: Radoslav Husar Priority: Critical Everything works in version with old subsytem with this settings (load is properly reported to balancer): {code:xml} <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> <mod-cluster-config advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp"> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> {code} Same configuration for latest snapshot doesn't work (load remains at 1): {code:xml} <subsystem xmlns="urn:jboss:domain:modcluster:4.0"> <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp"> <dynamic-load-provider> <load-metric type="cpu" weight="1"/> </dynamic-load-provider> </proxy> </subsystem> {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2891) Clean up dead social pages codes from kie-wb-common

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2891?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2891: --------------------------------- Description: This ticket aims to remove dead code found by Klara in this PR https://github.com/kiegroup/kie-wb-common/pull/1985. > Clean up dead social pages codes from kie-wb-common > --------------------------------------------------- > > Key: DROOLS-2891 > URL: https://issues.jboss.org/browse/DROOLS-2891 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > This ticket aims to remove dead code found by Klara in this PR https://github.com/kiegroup/kie-wb-common/pull/1985. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2891) Clean up dead social pages codes from kie-wb-common

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2891?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2891: --------------------------------- Description: This ticket aims to remove dead code found by [~kkufova] in this PR https://github.com/kiegroup/kie-wb-common/pull/1985. (was: This ticket aims to remove dead code found by Klara in this PR https://github.com/kiegroup/kie-wb-common/pull/1985.) > Clean up dead social pages codes from kie-wb-common > --------------------------------------------------- > > Key: DROOLS-2891 > URL: https://issues.jboss.org/browse/DROOLS-2891 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > This ticket aims to remove dead code found by [~kkufova] in this PR https://github.com/kiegroup/kie-wb-common/pull/1985. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2891) Clean up dead social pages codes from kie-wb-common

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2891: ------------------------------------ Summary: Clean up dead social pages codes from kie-wb-common Key: DROOLS-2891 URL: https://issues.jboss.org/browse/DROOLS-2891 Project: Drools Issue Type: Bug Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Clebert Suconic commented on WFWIP-90: -------------------------------------- [~mnovak] I just merged https://github.com/apache/activemq-artemis/pull/2248 on master Can you try it? > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2522: --------------------------------------- Sorry, I did not expressed myself well. I am terrible at graphical design, so I am *NOT* asking for the line widths to be thinner/slimmer. My comment was just that the current proportions between size, padding, alignment and line widths looked odd to me. I don't know what the solution is (it may or may not involve changing line widths), I am just asking it to be reviewed. :) > [DMN Designer] Palette aesthetics > --------------------------------- > > Key: DROOLS-2522 > URL: https://issues.jboss.org/browse/DROOLS-2522 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: UX, UXTeam > Attachments: palette.png > > > The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ] Clebert Suconic commented on WFWIP-90: -------------------------------------- There's an issue in Topology restart. the connection is wrongly issuing interrupts.. that's the same issue I recently came across on hornetq. So, this is likely not a regression. it's a fix needed both in 1.x and master > [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart > ------------------------------------------------------------------------------- > > Key: WFWIP-90 > URL: https://issues.jboss.org/browse/WFWIP-90 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- 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