[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4482?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-4482:
--------------------------------
Fix Version/s: 11.0.0.Beta3
(was: 11.0.0.Beta2)
> Out of the box SSL with Wildfly Elytron
> ---------------------------------------
>
> Key: WFCORE-4482
> URL: https://issues.jboss.org/browse/WFCORE-4482
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Major
> Labels: EAP-CD19
> Fix For: 11.0.0.Beta3
>
>
> The details of this RFE will be explored within the analysis, presently Undertow depends on a security-realm that generates a self signed cert on start up so we will require an Elytron equivalent.
> There may be opportunities to tie this in in some way with the new CA integration support but that can be explored in the analysis.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-944?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFCORE-944:
-------------------------------
Fix Version/s: 11.0.0.Beta3
(was: 11.0.0.Beta2)
> truststore path is ignored if provider is not JKS
> -------------------------------------------------
>
> Key: WFCORE-944
> URL: https://issues.jboss.org/browse/WFCORE-944
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Arto Huusko
> Priority: Major
> Fix For: 11.0.0.Beta3
>
>
> truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS.
> This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working.
> We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured.
> Even standard java supports PKCS12 truststores, where the same problem would occur.
> So I would suggest that
> - if provider is JKS, path is mandatory
> - if provider is not JKS, but path is specified, it is passed to the provider
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (WFCORE-4486) Support for multiple security realms - Failover
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4486?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-4486:
--------------------------------
Fix Version/s: 11.0.0.Beta3
(was: 11.0.0.Beta2)
> Support for multiple security realms - Failover
> -----------------------------------------------
>
> Key: WFCORE-4486
> URL: https://issues.jboss.org/browse/WFCORE-4486
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Priority: Major
> Labels: CD17-Deferred, EAP-CD19
> Fix For: 11.0.0.Beta3
>
>
> Our security realms are able to indicate unavailability by throwing a RealmUnavailableException
> We should support fail over to an alternative realm.
> A common request is fail over to a local file based realm if an LDAP or database server has gone down allowing administrators to retain access to the server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months
[JBoss JIRA] (DROOLS-4709) Remove surefire.forkCount for drools-compiler
by Tibor Zimanyi (Jira)
Tibor Zimanyi created DROOLS-4709:
-------------------------------------
Summary: Remove surefire.forkCount for drools-compiler
Key: DROOLS-4709
URL: https://issues.jboss.org/browse/DROOLS-4709
Project: Drools
Issue Type: Task
Components: core engine
Affects Versions: 7.29.0.Final
Reporter: Tibor Zimanyi
Assignee: Tibor Zimanyi
We have surefire.forkCount set to 2 for drools-compiler module. However this might produce problems with tests because drools-compiler contains a lot of multithreaded tests. For testing purposes, this forkCount should be removed from drools-compiler to see if it changes anything on Jenkins for the tests execution.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 4 months