October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4625: ------------------------------------------- [~danielezonca] Thanks for the steps, that helps. So yes we should add something to indicate a background error in the Test report panel (pie chart area) to indicate the errors. It would work with the icon at the tab, or if clear enough we could get rid of the tab icon. - If you could send me a screenshot of the current Report panel showing test errors, I can mockup an example that addresses incorporating the background error case. > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: background-error.png > > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3566) DMN:Detailed interactions for creating and managing DRDs

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3566?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3566: ------------------------------------------- Thanks [~manstis], and for finding that jira as well. :) > DMN:Detailed interactions for creating and managing DRDs > -------------------------------------------------------- > > Key: DROOLS-3566 > URL: https://issues.jboss.org/browse/DROOLS-3566 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: contextual-menu.png > > > Canvas node actions related to grouping and assigning to DRDs. > * As a user I want to easily select and group nodes on the canvas so that I can add them to a DRD or to create a new DRD. > (TBD) As a user I want to be able to be able to use the Navigator tree to create DRD's and assign canvas nodes, so that I can easily modify my graph views. > Notes: > Navigator Tree actions TBD: > * Drag nodes to DRDs. > * Contextual menu for tree objects? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12675) Upgrade WildFly Core 11.0.0.Beta1

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-12675: ---------------------------------- Summary: Upgrade WildFly Core 11.0.0.Beta1 Key: WFLY-12675 URL: https://issues.jboss.org/browse/WFLY-12675 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4449) Remove unused MultistepUtil methods

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4449?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4449: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Remove unused MultistepUtil methods > ----------------------------------- > > Key: WFCORE-4449 > URL: https://issues.jboss.org/browse/WFCORE-4449 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 11.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4419) Remove deprecated ParseUtil methods

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4419?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4419: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Remove deprecated ParseUtil methods > ----------------------------------- > > Key: WFCORE-4419 > URL: https://issues.jboss.org/browse/WFCORE-4419 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 11.0.0.Beta2 > > > Remove methods deprecated in WFCORE-4418. > When this is done the WFLYCTL0107 message method it calls should also be commented out. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4391) Upgrade apacheds-all to 2.0.0-M24 for Elytron tests

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4391?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4391: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Upgrade apacheds-all to 2.0.0-M24 for Elytron tests > --------------------------------------------------- > > Key: WFCORE-4391 > URL: https://issues.jboss.org/browse/WFCORE-4391 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 11.0.0.Beta2 > > > This upgrade is needed to avoid a race condition in Apache Directory Server that causes a hang in {{org.wildfly.extension.elytron.LdapTestCase}} with TLS 1.3. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[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.Beta2 (was: 11.0.0.Beta1) > 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.Beta2 > > > 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, 9 months

1
0
0 / 0

[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.Beta2 (was: 11.0.0.Beta1) > 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.Beta2 > > > 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)

6 years, 9 months

1
0
0 / 0

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

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4485?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4485: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Support for multiple security realms - Distributed Identities > ------------------------------------------------------------- > > Key: WFCORE-4485 > URL: https://issues.jboss.org/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.Beta2 > > > 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, 9 months

1
0
0 / 0

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

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4484?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4484: -------------------------------- Fix Version/s: 11.0.0.Beta2 (was: 11.0.0.Beta1) > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.jboss.org/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.Beta2 > > > 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, 9 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 October 2019