July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1844) Upgrade Commons CLI to version 1.4

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1844: ------------------------------------- Summary: Upgrade Commons CLI to version 1.4 Key: ELY-1844 URL: https://issues.jboss.org/browse/ELY-1844 Project: WildFly Elytron Issue Type: Component Upgrade Components: Command-Line Tool Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.10.0.CR3 As new commands are being developed should start with the latest version of the utility. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ELY-1843) The Digest NonceManager creates a ScheduledThreadPoolExecutor which is never shut down

by Tristan Tarrant (Jira)

Tristan Tarrant created ELY-1843: ------------------------------------ Summary: The Digest NonceManager creates a ScheduledThreadPoolExecutor which is never shut down Key: ELY-1843 URL: https://issues.jboss.org/browse/ELY-1843 Project: WildFly Elytron Issue Type: Bug Components: Authentication Mechanisms, HTTP Affects Versions: 1.9.1.Final Reporter: Tristan Tarrant The NonceManager creates a ScheduledThreadPoolExecutor in https://github.com/wildfly-security/wildfly-elytron/blob/master/http/dige... but there is no way to shut it down, thus resulting in a thread leak when stopping an application. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9614) Make keystore optional in SSO configuration

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-9614?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-9614: ---------------------------------------- It is actually likely this should be referencing a credential store. When it comes to anything involving signatures either their generation or validation another thing to consider is if we should have a service to perform that function without needing the actual keys to be used by multiple components. > Make keystore optional in SSO configuration > ------------------------------------------- > > Key: WFLY-9614 > URL: https://issues.jboss.org/browse/WFLY-9614 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Martin Choma > Priority: Major > > Keystore is required [1], thus signing logout message by default. > Questionable is if security brought by this is worth default command complexity as: > * Integrity of messages could be achieved on node to node communication level > * If message was not signed, attacker needs to know http session id to do a harm. Once attacker knows http session id, he can do a lot more useful attacks then logout user. > Some long communication on topic occured on Wildfly Elytron hipchat room 2017-12-7 - 2017-12-11. > [1] https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1898) Defining protocol of ssl config in security realm to incorrect value results in broken https

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-1898?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-1898. -------------------------------------- Resolution: Won't Fix Marking as won't fix as the legacy security realms are deprecated. > Defining protocol of ssl config in security realm to incorrect value results in broken https > -------------------------------------------------------------------------------------------- > > Key: WFCORE-1898 > URL: https://issues.jboss.org/browse/WFCORE-1898 > Project: WildFly Core > Issue Type: Enhancement > Components: Management, Security > Affects Versions: 3.0.0.Alpha10 > Reporter: Radim Hatlapatka > Priority: Major > Labels: user_experience > > If I define protocol to invalid value, it passes with success even though after reload it results in failure as such protocol isn't available. > It would be great if the value would be checked for proper values and fail the operation when incorrect value is provided. > E.g. this command {{/core-service=management/security-realm=ApplicationRealm/server-identity=ssl:write-attribute(name=protocol, value=ABC)}} should fail, but it passes, resulting that when doing reload https-listener and all dependent services fail to start > It would be beneficial to detect the incorrect value during the value update and rollback in case of invalid value being provided. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ] Stetson Robinson edited comment on DROOLS-4245 at 7/12/19 10:47 AM: -------------------------------------------------------------------- [~bdellasc], [~alexeylizunkov], It looks good to me. The main thing for me is for it to look mostly consistent with the BPMN "Documentation" content, and it seems like it is (I just looked at an example in the BC). Also, I can't comment on the Marvel page because I don't have an account (and am too lazy to set one up right now :) ) so just want to add a +1 to [~aglass] about Option A in the DRD components page, where the component header is repeated in the table harder. The tables need to be as complete as possible for optimal scanability. was (Author: stetson.robinson): [~bdellasc], [~alexeylizunkov], It looks good to me. The main thing for me is for it to look mostly consistent with the BPMN "Documentation" content, and it seems like it is. Also, I can't comment on the Marvel page because I don't have an account (and am too lazy to set one up right now :) ) so just want to add a +1 to [~aglass] about Option A in the DRD components page, where the component header is repeated in the table harder. The tables need to be as complete as possible for optimal scanability. > [DMN Designer] Documentation - Enhance presentation > --------------------------------------------------- > > Key: DROOLS-4245 > URL: https://issues.jboss.org/browse/DROOLS-4245 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: doc.pdf, new_doc.pdf > > > Enhance styles and presentation of the Documentation output. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation

by Stetson Robinson (Jira)

[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ] Stetson Robinson commented on DROOLS-4245: ------------------------------------------ [~bdellasc], [~alexeylizunkov], It looks good to me. The main thing for me is for it to look mostly consistent with the BPMN "Documentation" content, and it seems like it is. Also, I can't comment on the Marvel page because I don't have an account (and am too lazy to set one up right now :) ) so just want to add a +1 to [~aglass] about Option A in the DRD components page, where the component header is repeated in the table harder. The tables need to be as complete as possible for optimal scanability. > [DMN Designer] Documentation - Enhance presentation > --------------------------------------------------- > > Key: DROOLS-4245 > URL: https://issues.jboss.org/browse/DROOLS-4245 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: doc.pdf, new_doc.pdf > > > Enhance styles and presentation of the Documentation output. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5

by Amy Glass (Jira)

[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ] Amy Glass commented on DROOLS-4142: ----------------------------------- [~bdellasc] [~uxdlc] [~karreiro] I left this comment in the Marvel app, but posting here for visibility: I'm a little concerned about the discoverability and location of the Find/Search icon. Is there an icon that is just the magnifying glass alone? It's just not easy to see the magnifying glass denoting find due to its size and placement on the black page icon - and they look super small inside of that button or box. Do we have a tooltip on the icon as well and can that be specified in the design? Can this icon be used? https://fontawesome.com/icons/search?style=solid Can it be BLUE like the other icons (Properties and Doc icons, as well as the icons on the left side of the page)? When the tooltip is implemented, we should take care not to cover up other icons in that very crowded upper right corner. We've already experienced usability issues with tooltips for Properties and Doc covering up other things and making them inaccessible. > [GSS-RFE] UX design: Find feature in GDST/DMN 7.5 > ------------------------------------------------- > > Key: DROOLS-4142 > URL: https://issues.jboss.org/browse/DROOLS-4142 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png > > > This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. > h1. Requirements > See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9... > h1. Documentation > - Replace picture of GDT and DMN editor where they become obsolete > h1. Acceptance test > - Enter to large amount of data in search box > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - Searching for non-existing result > - Result appearing once > - Result appearing multiple times > - Set of inputs: > *- A-Z > *- a-z > *- 0-9 > *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + > *- Blank spaces -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4245: ------------------------------------------- Thanks [~bdellasc]!! When you have a chance to review this, please let us know if this meets the requirements [~tirelli] [~stetson.robinson] > [DMN Designer] Documentation - Enhance presentation > --------------------------------------------------- > > Key: DROOLS-4245 > URL: https://issues.jboss.org/browse/DROOLS-4245 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: doc.pdf, new_doc.pdf > > > Enhance styles and presentation of the Documentation output. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-665) Test case coverage for Istio

by Yuanlin Xu (Jira)

[ https://issues.jboss.org/browse/SWSQE-665?page=com.atlassian.jira.plugin.... ] Yuanlin Xu closed SWSQE-665. ---------------------------- > Test case coverage for Istio > ---------------------------- > > Key: SWSQE-665 > URL: https://issues.jboss.org/browse/SWSQE-665 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > Some areas are missing which we are not testing for Istio. Need to focus on that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-654) Istio-Investigate and work on automated/not automated/only manual type of test cases and mark them in polarion

by Yuanlin Xu (Jira)

[ https://issues.jboss.org/browse/SWSQE-654?page=com.atlassian.jira.plugin.... ] Yuanlin Xu closed SWSQE-654. ---------------------------- > Istio-Investigate and work on automated/not automated/only manual type of test cases and mark them in polarion > -------------------------------------------------------------------------------------------------------------- > > Key: SWSQE-654 > URL: https://issues.jboss.org/browse/SWSQE-654 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > Istio-Investigate and work on automated/not automated/only manual type of test cases and mark them in polarion -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 July 2019