December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-288) JWT signed by 1024 bit long key is rejected

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-288?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-288: ---------------------------------------- Ok this seems to be an ambiguity within the specification. So section 4.1 of the MP JWT specification states that "alg" must be set to "RS256". Then section 9.2 of the MP JWT specification states key sizes of 1024 and 2048 are required to be supported hence this bug report. However if I consult the RFE which defines the "RS256" algorithm is clearly states a minimum key size of 2048 bits: - https://tools.ietf.org/html/rfc7518#section-3.3 I suspect that section 9.2 of the specification may be from an older version and pre-date the requirement to use RS256, regardless I do not believe it would be intentional for the MP JWT spec to bypass the minimal key size so I will raise an issue against the specification. > JWT signed by 1024 bit long key is rejected > ------------------------------------------- > > Key: WFWIP-288 > URL: https://issues.redhat.com/browse/WFWIP-288 > Project: WildFly WIP > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Blocker > > According to MP-JWT 1.1 specification, 1024 and 2048 bit key sizes must be supported. Though when there is JWT signed by 1024 bit long key presented to the server, it is rejected and client receives "Unauthorized" (code 401) message. > See chapter 9.2. Supported Public Key Formats: > {quote} > Support for RSA Public Keys of 1024 or 2048 bits in length is required. Other key sizes are allowed, but should be considered vendor-specific. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4884) When a variable is reassigned in a consequence the property reactivity for the correspondent fact should be ignored

by Mario Fusco (Jira)

Mario Fusco created DROOLS-4884: ----------------------------------- Summary: When a variable is reassigned in a consequence the property reactivity for the correspondent fact should be ignored Key: DROOLS-4884 URL: https://issues.redhat.com/browse/DROOLS-4884 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco When a variable is reassigned in a consequence (not a good practice in general) the property reactivity for the correspondent fact should be ignored. In other word the following test should succeed. {code} @Test public void testReassignment() { final String str1 = "package com.example\n" + "\n" + "declare Counter\n" + " value1: int\n" + " value2: int\n" + "end\n" + "\n" + "rule \"Init\" when\n" + " not Counter()\n" + "then\n" + " drools.insert(new Counter(0, 0));\n" + "end\n" + "\n" + "rule \"Loop\"\n" + "when\n" + " $c: Counter( value1 == 0 )\n" + "then\n" + " $c = new Counter(0, 0);\n" + " $c.setValue2(1);\n" + " update($c);\n" + "end\n\n"; final KieSession ksession = new KieHelper().addContent( str1, ResourceType.DRL ) .build() .newKieSession(); assertEquals( 5, ksession.fireAllRules(5) ); } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4884) When a variable is reassigned in a consequence the property reactivity for the correspondent fact should be ignored

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4884?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4884: -------------------------------- Sprint: 2020 Week 01-03 (from Dec 30) > When a variable is reassigned in a consequence the property reactivity for the correspondent fact should be ignored > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4884 > URL: https://issues.redhat.com/browse/DROOLS-4884 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > When a variable is reassigned in a consequence (not a good practice in general) the property reactivity for the correspondent fact should be ignored. In other word the following test should succeed. > {code} > @Test > public void testReassignment() { > final String str1 = > "package com.example\n" + > "\n" + > "declare Counter\n" + > " value1: int\n" + > " value2: int\n" + > "end\n" + > "\n" + > "rule \"Init\" when\n" + > " not Counter()\n" + > "then\n" + > " drools.insert(new Counter(0, 0));\n" + > "end\n" + > "\n" + > "rule \"Loop\"\n" + > "when\n" + > " $c: Counter( value1 == 0 )\n" + > "then\n" + > " $c = new Counter(0, 0);\n" + > " $c.setValue2(1);\n" + > " update($c);\n" + > "end\n\n"; > final KieSession ksession = new KieHelper().addContent( str1, ResourceType.DRL ) > .build() > .newKieSession(); > assertEquals( 5, ksession.fireAllRules(5) ); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4884) When a variable is reassigned in a consequence the property reactivity for the correspondent fact should be ignored

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4884?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4884: -------------------------------- Sprint: 2019 Week 50-52 (from Dec 9) (was: 2020 Week 01-03 (from Dec 30)) > When a variable is reassigned in a consequence the property reactivity for the correspondent fact should be ignored > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4884 > URL: https://issues.redhat.com/browse/DROOLS-4884 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > When a variable is reassigned in a consequence (not a good practice in general) the property reactivity for the correspondent fact should be ignored. In other word the following test should succeed. > {code} > @Test > public void testReassignment() { > final String str1 = > "package com.example\n" + > "\n" + > "declare Counter\n" + > " value1: int\n" + > " value2: int\n" + > "end\n" + > "\n" + > "rule \"Init\" when\n" + > " not Counter()\n" + > "then\n" + > " drools.insert(new Counter(0, 0));\n" + > "end\n" + > "\n" + > "rule \"Loop\"\n" + > "when\n" + > " $c: Counter( value1 == 0 )\n" + > "then\n" + > " $c = new Counter(0, 0);\n" + > " $c.setValue2(1);\n" + > " update($c);\n" + > "end\n\n"; > final KieSession ksession = new KieHelper().addContent( str1, ResourceType.DRL ) > .build() > .newKieSession(); > assertEquals( 5, ksession.fireAllRules(5) ); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1038) VS Overview - HTTP Route automate

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1038?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1038: ---------------------------------- Sprint: Kiali Sprint #32 > VS Overview - HTTP Route automate > --------------------------------- > > Key: SWSQE-1038 > URL: https://issues.redhat.com/browse/SWSQE-1038 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1038) VS Overview - HTTP Route automate

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1038?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1038: ------------------------------------- Assignee: Hayk Hovsepyan > VS Overview - HTTP Route automate > --------------------------------- > > Key: SWSQE-1038 > URL: https://issues.redhat.com/browse/SWSQE-1038 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4880) JAXB serialize DomainClassMetadata classes

by Jiří Locker (Jira)

[ https://issues.redhat.com/browse/DROOLS-4880?page=com.atlassian.jira.plug... ] Jiří Locker updated DROOLS-4880: -------------------------------- Description: See https://github.com/kiegroup/droolsjbpm-integration/pull/1864/commits/2331... The Price class was moved from a static inner class because it was causing a JAXB problem in OptaPlannerIntegrationTest that crashed while trying to serialize DomainClassMetadata (due to the creation of the synthetic class CloudBalancingGenerator$1 Customers are still relying on static inner class so we should have this test running in the original form run the test with mvn -nsu -Dcontainer=wildfly -Dintegration-tests=true -Dfull=true -Dcontainer.profile=wildfly -Pwildfly clean install was: See https://github.com/kiegroup/droolsjbpm-integration/pull/1864/commits/2331... The Price class was moved from a static inner class because it was causing a JaxB problem in OptaPlannerIntegrationTest that crashed while trying to serialize DomainClassMetadata (due to the creation of the synthetic class CloudBalancingGenerator$1 Customers are still relying on static inner class so we should have this test running in the original form run the test with mvn -nsu -Dcontainer=wildfly -Dintegration-tests=true -Dfull=true -Dcontainer.profile=wildfly -Pwildfly clean install > JAXB serialize DomainClassMetadata classes > ------------------------------------------ > > Key: DROOLS-4880 > URL: https://issues.redhat.com/browse/DROOLS-4880 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > See > https://github.com/kiegroup/droolsjbpm-integration/pull/1864/commits/2331... > The Price class was moved from a static inner class because it was causing a JAXB problem in OptaPlannerIntegrationTest that crashed while trying to serialize DomainClassMetadata (due to the creation of the synthetic class CloudBalancingGenerator$1 > Customers are still relying on static inner class so we should have this test running in the original form > run the test with > mvn -nsu -Dcontainer=wildfly -Dintegration-tests=true -Dfull=true -Dcontainer.profile=wildfly -Pwildfly clean install -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4883) Test Scenario: create kie-docs content for Test Scenario Kie-server support

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4883: ------------------------------------- Summary: Test Scenario: create kie-docs content for Test Scenario Kie-server support Key: DROOLS-4883 URL: https://issues.redhat.com/browse/DROOLS-4883 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca Document how to enable test-scenario capability in Kie-server and how to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4880) JAXB serialize DomainClassMetadata classes

by Jiří Locker (Jira)

[ https://issues.redhat.com/browse/DROOLS-4880?page=com.atlassian.jira.plug... ] Jiří Locker updated DROOLS-4880: -------------------------------- Summary: JAXB serialize DomainClassMetadata classes (was: JaxB serialize DomainClassMetadata classes) > JAXB serialize DomainClassMetadata classes > ------------------------------------------ > > Key: DROOLS-4880 > URL: https://issues.redhat.com/browse/DROOLS-4880 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > See > https://github.com/kiegroup/droolsjbpm-integration/pull/1864/commits/2331... > The Price class was moved from a static inner class because it was causing a JaxB problem in OptaPlannerIntegrationTest that crashed while trying to serialize DomainClassMetadata (due to the creation of the synthetic class CloudBalancingGenerator$1 > Customers are still relying on static inner class so we should have this test running in the original form > run the test with > mvn -nsu -Dcontainer=wildfly -Dintegration-tests=true -Dfull=true -Dcontainer.profile=wildfly -Pwildfly clean install -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4882) [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4882?page=com.atlassian.jira.plug... ] Toni Rikkola moved AF-672 to DROOLS-4882: ----------------------------------------- Project: Drools (was: AppFormer) Key: DROOLS-4882 (was: AF-672) Component/s: Guided Decision Table Editor Guided Decision Tree Editor Guided Rule Editor Guided Score Card Editor Guided Template Editor (was: Data Model Oracle) > [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-4882 > URL: https://issues.redhat.com/browse/DROOLS-4882 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Decision Tree Editor, Guided Rule Editor, Guided Score Card Editor, Guided Template Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: reported-by-qe > > If the guided decision table uses fact field that has form 'xXxxx' then the generated getters and setters are incorrect. -- 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 December 2019