[JBoss JIRA] (DROOLS-2827) [DMN Designer] Diagram save produces svg
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2827:
-----------------------------------
Summary: [DMN Designer] Diagram save produces svg
Key: DROOLS-2827
URL: https://issues.jboss.org/browse/DROOLS-2827
Project: Drools
Issue Type: Bug
Components: DMN Editor
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: Screenshot from 2018-08-02 10-56-15.png
When user saves the diagram, the svg file appears in the workbench.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2755) [DMN Designer] Error when the user switches between DMN files
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2755:
--------------------------------
Description:
When the user switches between DMN files, the following error happens:
!demo.gif|thumbnail!
It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time.
h3. Manual Acceptance Test
Switch between multiple files
- using library
- using project explorer
was:
When the user switches between DMN files, the following error happens:
!demo.gif|thumbnail!
It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time.
> [DMN Designer] Error when the user switches between DMN files
> -------------------------------------------------------------
>
> Key: DROOLS-2755
> URL: https://issues.jboss.org/browse/DROOLS-2755
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: demo.gif
>
>
> When the user switches between DMN files, the following error happens:
> !demo.gif|thumbnail!
> It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time.
> h3. Manual Acceptance Test
> Switch between multiple files
> - using library
> - using project explorer
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2730) CSS for test "syntax cheatsheet" dock tab design
by Toni Rikkola (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2730?page=com.atlassian.jira.plugi... ]
Toni Rikkola edited comment on DROOLS-2730 at 8/2/18 4:40 AM:
--------------------------------------------------------------
[~ederign] Is it possible to tie the Docks to a screen and not to a perspective? At the moment for example the Data Modeller explorer uses Docks, but they do not show up unless your using the correct perspective.
For this reason for the Data Modeller is unusable in standalone mode.
was (Author: rikkola):
[~ederign] Is it possible to tie the Docks to a screen and not to a perspective? At the moment for example the Data Modeller explorer uses Docks, but they do not show up unless your using the correct perspective.
> CSS for test "syntax cheatsheet" dock tab design
> ------------------------------------------------
>
> Key: DROOLS-2730
> URL: https://issues.jboss.org/browse/DROOLS-2730
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Dock-deets.png, nospace.png, space.png
>
>
> As a practitioner I want to reference valid expression syntax, so that I can create expression formatted Given/Expect input values when creating a scenario test outline.
> *Verification conditions:*
> - CSS styles that employ relevant PatternFly styles.
> - CSS that articulates the design wireframe attached, and:
> https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476080, and:
> https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX...
> - Reviewed by scrum team prior to PR/dev delivery.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Martin Choma updated ELY-1621:
------------------------------
Steps to Reproduce:
- ./standalone.sh
- create BCFKS keystore keystore.bcfks. It is attached to JIRA as well
{code}
keytool \
-genkeypair\
-alias appserver\
-keyalg RSA\
-keysize 2048\
-keypass password\
-keystore /pat/to/keystore.bcfks\
-provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider\
-providerpath /pat/to/1.0.1/bc-fips-1.0.1.jar\
-storetype BCFKS\
-storepass password\
-dname CN=appserver,OU=QE,O=Redhat,L=Brno,ST=CR,C=CZ\
-validity 730\
-v
{code}
- run CLI with FIPS java
{code}
./jboss-cli.sh \
-c \
-Dwildfly.config.url=file:///from/attachment/cli-test-wildfly-config.xml \
--connect \
:read-attribute\(name=server-state\)
{code}
was:
- ./standalone.sh
- create BCFKS keystore. I attach it to JIRA as well
{code}
keytool \
-genkeypair\
-alias appserver\
-keyalg RSA\
-keysize 2048\
-keypass password\
-keystore /from/attachment/keystore.bcfks\
-provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider\
-providerpath /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.1/bc-fips-1.0.1.jar\
-storetype BCFKS\
-storepass password\
-dname CN=appserver,OU=QE,O=Redhat,L=Brno,ST=CR,C=CZ\
-validity 730\
-v
{code}
- run CLI with FIPS java
{code}
./jboss-cli.sh \
-c \
-Dwildfly.config.url=file:///from/attachment/cli-test-wildfly-config.xml \
--connect \
:read-attribute\(name=server-state\)
{code}
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> 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)
> 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.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1621?page=com.atlassian.jira.plugin.s... ]
Martin Choma updated ELY-1621:
------------------------------
Attachment: cli-test-wildfly-config.xml
jboss-cli.log
keystore.bcfks
> BC FIPS with CLI: the trustAnchors parameter must be non-empty
> --------------------------------------------------------------
>
> Key: ELY-1621
> URL: https://issues.jboss.org/browse/ELY-1621
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.1.Final
> Reporter: Martin Choma
> Priority: Blocker
> Attachments: cli-test-wildfly-config.xml, jboss-cli.log, keystore.bcfks
>
>
> I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
> {code:java|titlejboss-cli.log}
> 08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
> at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
> at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
> at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> 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)
> 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.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
> ... 14 more
> Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 16 more
> Caused by: java.security.KeyStoreException: initialization failed
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
> at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
> at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
> ... 22 more
> Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
> at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
> at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
> at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
> at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
> at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
> ... 25 more
> {code}
> When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
> I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
> When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
> So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1621) BC FIPS with CLI: the trustAnchors parameter must be non-empty
by Martin Choma (JIRA)
Martin Choma created ELY-1621:
---------------------------------
Summary: BC FIPS with CLI: the trustAnchors parameter must be non-empty
Key: ELY-1621
URL: https://issues.jboss.org/browse/ELY-1621
Project: WildFly Elytron
Issue Type: Bug
Components: SSL
Affects Versions: 1.5.1.Final
Reporter: Martin Choma
Priority: Blocker
I am trying to connect from jboss-cli.sh to EAP server. To reproduce the problem it is enough BC FIPS is used only on client side.
{code:java|titlejboss-cli.log}
08:13:18,469 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError
at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54)
at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286)
at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86)
at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146)
at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
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)
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.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36)
... 14 more
Caused by: org.wildfly.client.config.ConfigXMLParseException: java.security.KeyStoreException: initialization failed
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:525)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$11(ElytronXmlParser.java:711)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$13(ElytronXmlParser.java:749)
at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:356)
at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:231)
at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:192)
at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
... 16 more
Caused by: java.security.KeyStoreException: initialization failed
at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:150)
at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250)
at org.wildfly.security.auth.client.ElytronXmlParser$TrustManagerBuilder.build(ElytronXmlParser.java:590)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$10(ElytronXmlParser.java:523)
... 22 more
Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
at org.bouncycastle.jsse.provider.ProvX509TrustManagerImpl.<init>(ProvX509TrustManagerImpl.java:53)
at org.bouncycastle.jsse.provider.ProvTrustManagerFactorySpi.engineInit(ProvTrustManagerFactorySpi.java:146)
... 25 more
{code}
When I use non-FIPS java with CLI I can make it work. It does occure also when connecting to default unsecured port 9990.
I have double check truststore is there. Correct password is used. Server has permission to open the truststure. And truststore contains certificate
When I use BCFKS truststore on server side, e.g. in 2-way http communication it works.
So it looks to me something on client side is missing? Any hint?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months