May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-174) Openshift Clusters

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-174?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-174. ------------------------------------------- Resolution: Done > Openshift Clusters > ------------------ > > Key: SWSQE-174 > URL: https://issues.jboss.org/browse/SWSQE-174 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-259) Add minimal document for kiali-qe-rest framework

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-259?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-259: ------------------------------------------ Description: At this time, there is no document to understand What is kiali-qe-rest doing. Can you add minimal document? https://github.com/Kiali-QE/kiali-qe-rest acordling was: At this time, there is no document to understand What is kiali-qe-rest doing. Can you add minimal document? https://github.com/Kiali-QE/kiali-qe-rest > Add minimal document for kiali-qe-rest framework > ------------------------------------------------ > > Key: SWSQE-259 > URL: https://issues.jboss.org/browse/SWSQE-259 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Guilherme Baufaker Rêgo > > At this time, there is no document to understand What is kiali-qe-rest doing. Can you add minimal document? > https://github.com/Kiali-QE/kiali-qe-rest > acordling -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-259) Add minimal document for kiali-qe-rest framework

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-259?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-259: ------------------------------------------ Description: At this time, there is no document to understand What is kiali-qe-rest doing. Can you add minimal document? https://github.com/Kiali-QE/kiali-qe-rest was: At this time, there is no document to understand What is kiali-qe-rest doing. Can you add minimal document? https://github.com/Kiali-QE/kiali-qe-rest acordling > Add minimal document for kiali-qe-rest framework > ------------------------------------------------ > > Key: SWSQE-259 > URL: https://issues.jboss.org/browse/SWSQE-259 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Guilherme Baufaker Rêgo > > At this time, there is no document to understand What is kiali-qe-rest doing. Can you add minimal document? > https://github.com/Kiali-QE/kiali-qe-rest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2434) [DMN Designer] Navigator reaction on clear command

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2434?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2434: --------------------------------------- Attachment: DROOLS-2434-demo.gif > [DMN Designer] Navigator reaction on clear command > -------------------------------------------------- > > Key: DROOLS-2434 > URL: https://issues.jboss.org/browse/DROOLS-2434 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Attachments: DROOLS-2434-demo.gif, Screenshot from 2018-03-28 10-10-16.png, Screenshot from 2018-03-28 10-10-27.png, Screenshot from 2018-03-28 10-10-34.png, Screenshot from 2018-03-28 10-10-42.png > > > Clear of expression in DRD is not reflected in navigator. See steps to reproduce. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2434) [DMN Designer] Navigator reaction on clear command

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2434?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-2434: -------------------------------------------- [~jomarko] I could not reproduce this issue. See: !DROOLS-2434-demo.gif|thumbnail! Am I missing something? Thanks. > [DMN Designer] Navigator reaction on clear command > -------------------------------------------------- > > Key: DROOLS-2434 > URL: https://issues.jboss.org/browse/DROOLS-2434 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Attachments: DROOLS-2434-demo.gif, Screenshot from 2018-03-28 10-10-16.png, Screenshot from 2018-03-28 10-10-27.png, Screenshot from 2018-03-28 10-10-34.png, Screenshot from 2018-03-28 10-10-42.png > > > Clear of expression in DRD is not reflected in navigator. See steps to reproduce. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-263) Kiali Istio Checker Job may not be working

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-263?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-263: --------------------------------------------- Assignee: (was: Michael Foley) > Kiali Istio Checker Job may not be working > ------------------------------------------- > > Key: SWSQE-263 > URL: https://issues.jboss.org/browse/SWSQE-263 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > > I think Kiali Istio Checker is not running fine > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... > Running > Current istio-ca pod status : Running > scripts/kiali/testscript.sh: line 55: [: too many arguments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-263) Kiali Istio Checker Job may not be working

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-263: --------------------------------------------- Summary: Kiali Istio Checker Job may not be working Key: SWSQE-263 URL: https://issues.jboss.org/browse/SWSQE-263 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley I think Kiali Istio Checker is not running fine http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... Running Current istio-ca pod status : Running scripts/kiali/testscript.sh: line 55: [: too many arguments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2433) [DMN Designer] Can not click to canvas after DRD navigation undo

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2433?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-2433: -------------------------------------------- [~jomarko] I could not reproduce this issue. See: !DROOLS-2433-demo.gif|thumbnail! Am I missing something? Thanks. > [DMN Designer] Can not click to canvas after DRD navigation undo > ---------------------------------------------------------------- > > Key: DROOLS-2433 > URL: https://issues.jboss.org/browse/DROOLS-2433 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Attachments: DROOLS-2433-demo.gif, Screenshot from 2018-03-28 09-52-37.png > > > If user undo action "Navigate to DRD", then he will be unable to click on canvas. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2433) [DMN Designer] Can not click to canvas after DRD navigation undo

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2433?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2433: --------------------------------------- Attachment: DROOLS-2433-demo.gif > [DMN Designer] Can not click to canvas after DRD navigation undo > ---------------------------------------------------------------- > > Key: DROOLS-2433 > URL: https://issues.jboss.org/browse/DROOLS-2433 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Attachments: DROOLS-2433-demo.gif, Screenshot from 2018-03-28 09-52-37.png > > > If user undo action "Navigate to DRD", then he will be unable to click on canvas. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9892) Upgrade org.apache.santuario.xmlsec to 2.1.1. caused regression in PicketLinkSTS

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9892?page=com.atlassian.jira.plugin.... ] Sande Gilda edited comment on WFLY-9892 at 5/28/18 2:23 PM: ------------------------------------------------------------ [~kabirkhan]: I have added [~emmartins] since he is the engineering lead for the quickstarts and is more familiar with the engineering impact. [~emmartins]: Should we create a Wildfly quickstart JIRA for this one? [~kabirkhan] and [~pcraveiro]: It sounds like I need to create an issue for the 7.2 Migration Guide for this. Do you agree? One question I have is how did the #13 get in the file? Did the customer add it? Was it generated? was (Author: sgilda): [~kabirkhan]: I have added [~emmartins] since he is the engineering lead for the quickstarts and is more familiar with the engineering impact. [~emmartins]: Should we create a Wildfly quickstart JIRA for this one? [~kabirkhan] and [~pcraveiro]: It sounds like I need to create an issue for the 7.2 Migration Guide for this. Do you agree? > Upgrade org.apache.santuario.xmlsec to 2.1.1. caused regression in PicketLinkSTS > -------------------------------------------------------------------------------- > > Key: WFLY-9892 > URL: https://issues.jboss.org/browse/WFLY-9892 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 12.0.0.Beta1 > Reporter: Ondrej Lukas > Assignee: Pedro Igor > Priority: Blocker > Attachments: ejb-security-picketlink.zip, ejb-test.jar, picketlink-sts.war, sts-config.properties > > > When token from PicketLink STS is issued and signed then it is not able to be used for authentication through Remoting in WildFly 12 (i.e. it cannot be set as {{remote.connection.main.password}} property which can be used in PicketLink {{org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule}}). It seems it is caused by upgrade of org.apache.santuario.xmlsec to version 2.1.1. [1]. When WILDFLY11_HOME/modules/system/layers/base/org/apache/santuario/xmlsec/main/xmlsec-2.0.8.jar is placed to WildFly 12 modules then it works correctly. > We report it as a blocker since it is regression - application which works correctly on WildFly 11 stops to work on WildFly 12 - users are not able to authenticate through Remoting with signed tokens from PicketLink STS correctly. > Remoting fails due to following exception: > {code} > java.lang.IllegalArgumentException: ELY05131: Invalid ASCII control "0xA" > at org.wildfly.security.sasl.util.StringPrep.forbidAsciiControl(StringPrep.java:117) > at org.wildfly.security.sasl.util.StringPrep.encode(StringPrep.java:295) > at org.wildfly.security.sasl.util.StringPrep.encode(StringPrep.java:196) > at org.wildfly.security.sasl.plain.PlainSaslClient.evaluateChallenge(PlainSaslClient.java:95) > at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55) > at java.security.AccessController.doPrivileged(Native Method) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.lambda$handleEvent$1(ClientConnectionOpenListener.java:460) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > {code} > It is caused by different formating value of SignatureValue in assertion. In WildFly 11 SignatureValue looks like: > {code} > <dsig:SignatureValue xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">nFVkKrXTyYEQ9cwc9OOgySYebEtwzw4alVYP0viXzvqZAUAKtAXEBAfDB8xIOms78twlDdq79MiSvk8OrOdf126Kw/IR8JRn1fYyZ5tsIRcNoTXMgGaTqhrn/HKlLqqqHhVHrJURunqkSzTTxylA2AEPhEDD5Y7hS0W2ZZCeSvuri+PRDSTrRnuedz0yQuHQu1mZ0gjoEFbHh4Wkkn5Ac1R4gmewmmzPud+ZE6Ux4YpeHzQ8rAvZ4bDk6j+eQIRsSxFTLo5RSA3FWN8+lUNV/CSRqBPXsK7QxOaTdBgF+4NXWeExrNJ9SeVFcf9yelvReAtR2JNZ6DUY8u45KtXmLw==</dsig:SignatureValue> > {code} > In WildFly 12 it looks like (there are end of lines): > {code} > <dsig:SignatureValue xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">cUNpFJIZlLYrBDZtQSTDrq2K6PbnAHyg2qbx/D5FuB4XMjdQ5oxQjkMejLyelnA7s4GFusoLhahl > qlTOT8UrOyxrR4yYAmJ/e5s+f4gys926+tbiraT/3/wG8wM/Lvcjvk5Ap69zODuRYpypsWfA4jrI > 7TTBXVPGy8g4KUdnFviUiTuFTc2Ghgxp53AmUuLis/THyP28jE7+28//q8bi/bQrFwHC6tWX67+N > K1duFCOcQ6IPIKeVrePZz55Ivgl+WWdkF6uYCz5IdMzurhzmeQ3K8DAMIxz/MG67VWJIOnuGNWF7 > nmdye5zd9AFcRsr1XadvZJCbGNfuc89AL5inCg==</dsig:SignatureValue> > {code} > [1] https://github.com/wildfly/wildfly/commit/536de514829f2187abf1126c8916a04... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 May 2018