[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ]
Jan Kalina commented on ELY-1639:
---------------------------------
[~mchoma] yes, this is correct - the alias choosing is possible only using elytron specific KeyManager (which is not allowed in FIPS)
> 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: Jan Kalina
> Priority: Blocker
> Attachments: cli-wildfly-config.xml
>
>
> 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
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2888:
-------------------------------------
[~karreiro] I was thinking that the "Add" inline option would be available on all rows, so if the user is in the middle of a long list they don't have to go to the primary Add button at the top of the page, which navigates them to the bottom, then find their way back to the middle... As far as the action on the Header of the Structured row - it would also have the inline Add kebab option, but to avoid confusion we could perhaps add an additional menu option for just this header row - maybe Add row, Add row structure, (with better labels). Wdyt?
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: previous.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2795) [DMN Designer] Data-types: Grid: DecisionTable
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2795?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2795:
-----------------------------------
Description:
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (/) {{InputClause}} columns header should show Input Data Type
- (/) {{InputClause}} columns should support changing the Input Data Type
- (/) {{OutputClause}} columns header should show Output Data Type
- (/) {{OutputClause}} columns should support changing the Output Data Type
was:
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (/) {{InputClause}} columns header should show Input Data Type
- (/) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Output Data Type
- (x) {{OutputClause}} columns should support changing the Output Data Type
> [DMN Designer] Data-types: Grid: DecisionTable
> ----------------------------------------------
>
> Key: DROOLS-2795
> URL: https://issues.jboss.org/browse/DROOLS-2795
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> *_Decision Table_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
> - (/) {{InputClause}} columns header should show Input Data Type
> - (/) {{InputClause}} columns should support changing the Input Data Type
> - (/) {{OutputClause}} columns header should show Output Data Type
> - (/) {{OutputClause}} columns should support changing the Output Data Type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2889) Research accessibility considerations for Data Type list drag-n-drop.
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2889?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-2889:
---------------------------------------
[~srambach] to be honest, I think that would actually be a good feature. We can do it later if that makes it easy but here is a very common scenario:
1. user creates a tPerson data type that contains, as one of its field, "address", that is a structure with street and city fields. E.g.:
* tPerson
** name (string)
** age (number)
** address (structure)
*** street (string)
*** city (string)
2. user creates a tBusiness data type and realizes he needs an address there as well
* tBusiness
** business name (string)
** address (?????)
3. instead of duplicating the definition of address, he could just drag the address from the person and make a new type "tAddress" and then use that in both datatypes. end result would be:
* tPerson
** name (string)
** age (number)
** address (tAddress)
* tAddress
** street (string)
** city (string)
* tBusiness
** business name (string)
** address (tAddress)
> Research accessibility considerations for Data Type list drag-n-drop.
> ----------------------------------------------------------------------
>
> Key: DROOLS-2889
> URL: https://issues.jboss.org/browse/DROOLS-2889
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-13 at 1.42.16 PM.png
>
>
> Use Case: As a DMN user I will want to be able to reorder the list of Custom data types so that I can arrange data types in a logical order.
> Notes:
> * The Data Type dialog leverage the following PR list pattern:
> https://www.patternfly.org/pattern-library/content-views/tree-list-view
> * The list will need to be re-orderable, there is an open design jira to determine the interaction options for that feature.
> * Design is currently being iterated upon, but last iteration wireframes are posted at: https://redhat.invisionapp.com/share/B7NEEUSV539
> Verification conditions:
> * Research results summarized in the jira or a linked google doc., etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10873) Duplicated httpcomponent jars in WF 14.0.0.Beta2
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-10873?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet commented on WFLY-10873:
------------------------------------------
[~msvehla]no problem, I thought it was already affected to me ;)
> Duplicated httpcomponent jars in WF 14.0.0.Beta2
> ------------------------------------------------
>
> Key: WFLY-10873
> URL: https://issues.jboss.org/browse/WFLY-10873
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 14.0.0.Beta2
> Reporter: Martin Švehla
> Assignee: ehsavoie Hugonnet
>
> In current Beta2 build, I see duplicated httpclient and httpcore jars. The new org.apache.httpcomponents.core module was added that introduced this duplication.
> in 14.0.0.Beta2:
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> ├── core
> │ └── main
> │ ├── httpclient-4.5.2.jar
> │ ├── httpcore-4.4.4.jar
> │ └── module.xml
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
> In WF 13.0.0.Final
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-7112) Allow optional tag virtual-host (and others) inside jboss-app.xml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7112?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-7112:
-----------------------------------
Component/s: Web (Undertow)
> Allow optional tag virtual-host (and others) inside jboss-app.xml
> -----------------------------------------------------------------
>
> Key: WFLY-7112
> URL: https://issues.jboss.org/browse/WFLY-7112
> Project: WildFly
> Issue Type: Feature Request
> Components: EE, Web (Undertow)
> Affects Versions: 10.1.0.Final
> Reporter: Guido Jäkel
> Assignee: Jason Greene
>
> With undertow, the assignment of a web-application to a virtual host must be set in {{$WAR/META-INF/jboss-web.xml}}. A very adjacent parameter, the context-root, might be defined or overridden here, too.
> In practice, for a concrete deployment generally one have to adapt both parts of the URL, the (virtual) host and the context-root part and may use this file and e.g. apply it with the overlay feature.
> In case of an EAR, its components are declared inside {{$EAR/META-INF/application.xml}}. For an web application, the {{context-root}} is defined here. I found, that this have precedence to a {{$WAR/WEB-INF/jboss-web.xml}}. I don't expect this, but it might be defined by JEE specifications in that way. If not, this feature request should be converted to a bug report concerning a wrong preference order.
> To my knowledge, at the moment this file seems the only way to set the {{virtual-host}} to use. And this looks very inconsistent to me, because you have to use two different "far-out" files to controll this very associated informations.
> The informations in application.xml may be overridden and enriched by {{jboss-appl.xml}} in a similar manner as with {{web.xml}} and {{jboss-web.xml}}. I would expect (and suggest it as a feature) to define the virtual host here in an analogous way as the context root in {{application.xml}} may be overriden here.
> {code}
> <module>
> <web>
> <web-uri>a.war</web-uri>
> <context-root>/foo</context-root>
> <virtual-host>a.domain.tld</virtual-host>
> ...
> </web>
> </module>
> {code}
> This concept should be probably expanded to the complete feature set controlled by the {{jboss-web.xml}}, like undertow-related like {{server-instance}} or others like {{security-domain}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10873) Duplicated httpcomponent jars in WF 14.0.0.Beta2
by Martin Švehla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10873?page=com.atlassian.jira.plugin... ]
Martin Švehla commented on WFLY-10873:
--------------------------------------
[~ehugonnet] I assigned this to you since Jason is busy and as mentioned it seems your commit introduced the duplication
[~kabirkhan], [~jamezp], [~jmesnil] FYI ^^
> Duplicated httpcomponent jars in WF 14.0.0.Beta2
> ------------------------------------------------
>
> Key: WFLY-10873
> URL: https://issues.jboss.org/browse/WFLY-10873
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 14.0.0.Beta2
> Reporter: Martin Švehla
> Assignee: ehsavoie Hugonnet
>
> In current Beta2 build, I see duplicated httpclient and httpcore jars. The new org.apache.httpcomponents.core module was added that introduced this duplication.
> in 14.0.0.Beta2:
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> ├── core
> │ └── main
> │ ├── httpclient-4.5.2.jar
> │ ├── httpcore-4.4.4.jar
> │ └── module.xml
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
> In WF 13.0.0.Final
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10873) Duplicated httpcomponent jars in WF 14.0.0.Beta2
by Martin Švehla (JIRA)
[ https://issues.jboss.org/browse/WFLY-10873?page=com.atlassian.jira.plugin... ]
Martin Švehla reassigned WFLY-10873:
------------------------------------
Assignee: ehsavoie Hugonnet (was: Jason Greene)
> Duplicated httpcomponent jars in WF 14.0.0.Beta2
> ------------------------------------------------
>
> Key: WFLY-10873
> URL: https://issues.jboss.org/browse/WFLY-10873
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 14.0.0.Beta2
> Reporter: Martin Švehla
> Assignee: ehsavoie Hugonnet
>
> In current Beta2 build, I see duplicated httpclient and httpcore jars. The new org.apache.httpcomponents.core module was added that introduced this duplication.
> in 14.0.0.Beta2:
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> ├── core
> │ └── main
> │ ├── httpclient-4.5.2.jar
> │ ├── httpcore-4.4.4.jar
> │ └── module.xml
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
> In WF 13.0.0.Final
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10873) Duplicated httpcomponent jars in WF 14.0.0.Beta2
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10873?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda commented on WFLY-10873:
------------------------------------------
https://github.com/wildfly/wildfly-core/commits/master/core-feature-pack/... says it's [~ehugonnet] who introduced that to core
> Duplicated httpcomponent jars in WF 14.0.0.Beta2
> ------------------------------------------------
>
> Key: WFLY-10873
> URL: https://issues.jboss.org/browse/WFLY-10873
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 14.0.0.Beta2
> Reporter: Martin Švehla
> Assignee: Jason Greene
>
> In current Beta2 build, I see duplicated httpclient and httpcore jars. The new org.apache.httpcomponents.core module was added that introduced this duplication.
> in 14.0.0.Beta2:
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> ├── core
> │ └── main
> │ ├── httpclient-4.5.2.jar
> │ ├── httpcore-4.4.4.jar
> │ └── module.xml
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
> In WF 13.0.0.Final
> {code}
> $ tree modules/system/layers/base/org/apache/httpcomponents/
> modules/system/layers/base/org/apache/httpcomponents/
> └── main
> ├── httpasyncclient-4.1.3.jar
> ├── httpclient-4.5.2.jar
> ├── httpcore-4.4.4.jar
> ├── httpcore-nio-4.4.4.jar
> ├── httpmime-4.5.2.jar
> └── module.xml
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months