January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3502) ScoringStrategiesTest, ScorecardProviderTest, ExternalObjectModelTest, ScoreCardProviderPMMLTest, ScoreCardReasonCodeTest fail on Windows

by Jiri Petrlik (Jira)

[ https://issues.redhat.com/browse/DROOLS-3502?page=com.atlassian.jira.plug... ] Jiri Petrlik commented on DROOLS-3502: -------------------------------------- [~gabriolo] Thank you for info! Please keep me updated! > ScoringStrategiesTest, ScorecardProviderTest, ExternalObjectModelTest, ScoreCardProviderPMMLTest, ScoreCardReasonCodeTest fail on Windows > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3502 > URL: https://issues.redhat.com/browse/DROOLS-3502 > Project: Drools > Issue Type: Bug > Components: PMML > Affects Versions: 7.16.0.Final > Reporter: Tibor Zimanyi > Assignee: Gabriele Cardosi > Priority: Major > > When running mentioned tests on Windows environment, it fails with following output [1]. > [1] https://gist.github.com/baldimir/f93f32a8e3855205433153712cb3baae -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3502) ScoringStrategiesTest, ScorecardProviderTest, ExternalObjectModelTest, ScoreCardProviderPMMLTest, ScoreCardReasonCodeTest fail on Windows

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-3502?page=com.atlassian.jira.plug... ] Gabriele Cardosi commented on DROOLS-3502: ------------------------------------------ [~jpetrlik] Hi Jiri. I've just been assigned all those tickets. Right now I'm not sure if this will be valid anymore or will be closed/replaced. > ScoringStrategiesTest, ScorecardProviderTest, ExternalObjectModelTest, ScoreCardProviderPMMLTest, ScoreCardReasonCodeTest fail on Windows > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3502 > URL: https://issues.redhat.com/browse/DROOLS-3502 > Project: Drools > Issue Type: Bug > Components: PMML > Affects Versions: 7.16.0.Final > Reporter: Tibor Zimanyi > Assignee: Gabriele Cardosi > Priority: Major > > When running mentioned tests on Windows environment, it fails with following output [1]. > [1] https://gist.github.com/baldimir/f93f32a8e3855205433153712cb3baae -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12885) Upgrade JSF based on Mojarra 2.3.9.SP05 to ...

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12885?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12885: --------------------------------- Summary: Upgrade JSF based on Mojarra 2.3.9.SP05 to ... (was: Upgrade JSF based on Mojarra 2.3.9.SP05-redhat-00001 to ...) > Upgrade JSF based on Mojarra 2.3.9.SP05 to ... > ---------------------------------------------- > > Key: WFLY-12885 > URL: https://issues.redhat.com/browse/WFLY-12885 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4934) Multistatement support for MVEL Expressions

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4934?page=com.atlassian.jira.plug... ] Daniele Zonca moved BAPL-1510 to DROOLS-4934: --------------------------------------------- Project: Drools (was: Business Automation Planning) Key: DROOLS-4934 (was: BAPL-1510) Workflow: GIT Pull Request workflow (was: CDW with docs v1) QE Status: NEW > Multistatement support for MVEL Expressions > ------------------------------------------- > > Key: DROOLS-4934 > URL: https://issues.redhat.com/browse/DROOLS-4934 > Project: Drools > Issue Type: Bug > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12962) Upgrade WildFly Core 11.0.0.Beta7

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-12962: ---------------------------------- Summary: Upgrade WildFly Core 11.0.0.Beta7 Key: WFLY-12962 URL: https://issues.redhat.com/browse/WFLY-12962 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3376) Modules may create loggers on a deployments log context

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-3376?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-3376: -------------------------------- Fix Version/s: 11.0.0.Beta8 (was: 11.0.0.Beta7) > Modules may create loggers on a deployments log context > ------------------------------------------------------- > > Key: WFCORE-3376 > URL: https://issues.redhat.com/browse/WFCORE-3376 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Fix For: 11.0.0.Beta8 > > > Currently WildFly uses a {{ClassLoaderLogContextSelector}} to determine the log context to use when creating loggers. If a deployment has it's own log context, via logging-profile or per-deployment logging, and a dependency on a module, that module may create loggers on the deployments log context. This is due to the fact the the call stack is walked until it finds a log context associated with a class loader. > What is needed is a way to short-circuit once a non-logging API class loader is found and determine if there is an associated log context with the callers class loader. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-944?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-944: ------------------------------- Fix Version/s: 11.0.0.Beta8 (was: 11.0.0.Beta7) > truststore path is ignored if provider is not JKS > ------------------------------------------------- > > Key: WFCORE-944 > URL: https://issues.redhat.com/browse/WFCORE-944 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Arto Huusko > Priority: Major > Fix For: 11.0.0.Beta8 > > > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4484) Support SSH authentication for Git persistence

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4484?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4484: -------------------------------- Fix Version/s: 11.0.0.Beta8 (was: 11.0.0.Beta7) > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.redhat.com/browse/WFCORE-4484 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Farah Juma > Assignee: Ashley Abdel-Sayed > Priority: Major > Labels: EAP-CD19 > Fix For: 11.0.0.Beta8 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4482?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4482: -------------------------------- Fix Version/s: 11.0.0.Beta8 (was: 11.0.0.Beta7) > Out of the box SSL with Wildfly Elytron > --------------------------------------- > > Key: WFCORE-4482 > URL: https://issues.redhat.com/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.Beta8 > > > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4485) Support for multiple security realms - Distributed Identities

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4485?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4485: -------------------------------- Fix Version/s: 11.0.0.Beta8 (was: 11.0.0.Beta7) > Support for multiple security realms - Distributed Identities > ------------------------------------------------------------- > > Key: WFCORE-4485 > URL: https://issues.redhat.com/browse/WFCORE-4485 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > Labels: CD17-Deferred, EAP-CD19, Previous_RFE > Fix For: 11.0.0.Beta8 > > > By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list. > This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together. > Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged. > This RFE is not about fail over in the event of a realm being unavailable although it may be related. > This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 January 2020