[JBoss JIRA] (ELY-1648) FIPS NoSuchAlgorithmException: JKS KeyStore not available when trustmanager SunX509
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1648?page=com.atlassian.jira.plugin.s... ]
Justin Cook commented on ELY-1648:
----------------------------------
[~mchoma] I've been unable to reproduce the exception. Running in FIPS mode with supplied configuration results in:
{code}
wfcli -c -Dwildfly.config.url=cli-test-wildfly-config.xml :read-attribute\(name=server-state\)
{
"outcome" => "success",
"result" => "running"
}
{code}
With no exceptions thrown in the server log.
> FIPS NoSuchAlgorithmException: JKS KeyStore not available when trustmanager SunX509
> -----------------------------------------------------------------------------------
>
> Key: ELY-1648
> URL: https://issues.jboss.org/browse/ELY-1648
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.5.5.Final
> Reporter: Martin Choma
> Assignee: Justin Cook
> Attachments: java.security
>
>
> With SunX509 truststore algorithm I can succesfully connect with CLI.
> {code}
> <configuration>
> <authentication-client xmlns="urn:elytron:client:1.1">
> <key-stores>
> <key-store name="truststore" type="PKCS11">
> <key-store-clear-password password="${password}" />
> </key-store>
> </key-stores>
> <ssl-contexts>
> <ssl-context name="client-cli-context">
> <trust-manager algorithm="SunX509" />
> <trust-store key-store-name="truststore" />
> <cipher-suite selector="${cipher.suite.filter}" />
> <protocol names="${protocol}" />
> </ssl-context>
> </ssl-contexts>
> <ssl-context-rules>
> <rule use-ssl-context="client-cli-context" />
> </ssl-context-rules>
> </authentication-client>
> </configuration>
> {code}
> But there is a exception in log
> {code}
> 13:58:27,652 INFO [com.redhat.eap.qe.cli.CustomCLIExecutor] (main) java.security.KeyStoreException: JKS not found
> at java.security.KeyStore.getInstance(KeyStore.java:851)
> at sun.security.util.AnchorCertificates$1.run(AnchorCertificates.java:59)
> at sun.security.util.AnchorCertificates$1.run(AnchorCertificates.java:52)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.util.AnchorCertificates.<clinit>(AnchorCertificates.java:52)
> at sun.security.provider.certpath.AlgorithmChecker.checkFingerprint(AlgorithmChecker.java:214)
> at sun.security.provider.certpath.AlgorithmChecker.<init>(AlgorithmChecker.java:164)
> at sun.security.provider.certpath.AlgorithmChecker.<init>(AlgorithmChecker.java:118)
> at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:157)
> at sun.security.validator.Validator.validate(Validator.java:260)
> at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:281)
> at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1601)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052)
> at sun.security.ssl.Handshaker$1.run(Handshaker.java:992)
> at sun.security.ssl.Handshaker$1.run(Handshaker.java:989)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1467)
> at org.xnio.ssl.JsseSslConduitEngine.handleHandshake(JsseSslConduitEngine.java:543)
> at org.xnio.ssl.JsseSslConduitEngine.wrap(JsseSslConduitEngine.java:314)
> at org.xnio.ssl.JsseSslConduitEngine.wrap(JsseSslConduitEngine.java:204)
> at org.xnio.ssl.JsseSslStreamSinkConduit.write(JsseSslStreamSinkConduit.java:98)
> at org.xnio.ssl.JsseSslStreamSinkConduit.write(JsseSslStreamSinkConduit.java:72)
> at org.xnio.conduits.ConduitStreamSinkChannel.write(ConduitStreamSinkChannel.java:150)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:385)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:372)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.writeReady(WriteReadyHandler.java:65)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:94)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> Caused by: java.security.NoSuchAlgorithmException: JKS KeyStore not available
> at sun.security.jca.GetInstance.getInstance(GetInstance.java:159)
> at java.security.Security.getImpl(Security.java:695)
> at java.security.KeyStore.getInstance(KeyStore.java:848)
> ... 31 more
> {code}
> When I change SunX509 to PKIX exception does not occure anymore.
> Seems exception is thrown by code https://github.com/JetBrains/jdk8u_jdk/blob/master/src/share/classes/sun/...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration option component
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3021:
---------------------------------------
Sprint: (was: 2018 Week 42-44)
> [DMN Designer] Data Types - Constraints - Enumeration option component
> ----------------------------------------------------------------------
>
> Key: DROOLS-3021
> URL: https://issues.jboss.org/browse/DROOLS-3021
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: enumaration-component.png
>
>
> - When "Enumeration" is selected in the _Base Component_, the _Enumeration component_ must be loaded;
> - The _Enumeration component_ is an input that creates "tags" when the user presses "Enter", the UI component must look like this:
> !enumaration-component.png|thumbnail!
> - The field (for creating a tag), must show the appropriated widget for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - When the user clicks in a tag, it must be removed.
> - When the user clicks in the Data Type "Save" button, the values (tags) must be persisted in the Data Type.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types
by Guilherme Carreiro (JIRA)
Guilherme Carreiro created DROOLS-3024:
------------------------------------------
Summary: [DMN Designer] Data Types - Add nested data types
Key: DROOLS-3024
URL: https://issues.jboss.org/browse/DROOLS-3024
Project: Drools
Issue Type: Task
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Guilherme Carreiro
Attachments: options.png
- The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
!options.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3023) [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3023?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3023:
---------------------------------------
Description:
1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
- tPerson
-- uuid
-- name
-- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
--- uuid
--- name
----
2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
- tCity <-- If the user removes this Data Type
-- uuid
-- name
- tPerson
-- uuid
-- name
-- city (tCity) <-- This field will be removed too..
--- uuid <-- ..and consequently..
--- name <-- ..these two will be removed too.
was:
1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
- tPerson
-- uuid
-- name
-- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
--- uuid
--- name
2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
- tCity <-- If the user removes this Data Type
-- uuid
-- name
- tPerson
-- uuid
-- name
-- city (tCity) <-- This field will be removed too..
--- uuid <-- ..and consequently..
--- name <-- ..these two will be removed too.
> [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3023
> URL: https://issues.jboss.org/browse/DROOLS-3023
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> 1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
> - tPerson
> -- uuid
> -- name
> -- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
> --- uuid
> --- name
> ----
> 2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
> - tCity <-- If the user removes this Data Type
> -- uuid
> -- name
> - tPerson
> -- uuid
> -- name
> -- city (tCity) <-- This field will be removed too..
> --- uuid <-- ..and consequently..
> --- name <-- ..these two will be removed too.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3022:
---------------------------------------
Description:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
----
Prototype:
!validation.png|thumbnail!
was:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
---
Prototype:
!validation.png|thumbnail!
> [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3022
> URL: https://issues.jboss.org/browse/DROOLS-3022
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: validation.png
>
>
> The Data Type name must be unique at the level that it's defined; e.g.
> - tPerson
> -- uuid
> -- name
> -- city (Structure)
> --- uuid
> --- name
> The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
> ----
> Prototype:
> !validation.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months