January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12836) Large allocations in EJBContextImpl#isCallerInRole

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/WFLY-12836?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed updated WFLY-12836: -------------------------------------- Attachment: screenshot-1.png > Large allocations in EJBContextImpl#isCallerInRole > -------------------------------------------------- > > Key: WFLY-12836 > URL: https://issues.redhat.com/browse/WFLY-12836 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Affects Versions: 18.0.1.Final > Reporter: Philippe Marschall > Assignee: Ashley Abdel-Sayed > Priority: Major > Attachments: elytron_allocations_redacted.PNG, screenshot-1.png > > > In our application we have the need to know the roles of the current user. We would like to do this using Java / Jakarta EE APIs rather than rely on WildFly implementation classes. We do this by iterating over all roles, which we know statically, and calling {{EJBContext#isCallerInRole}} for each one. This seem to be a common technique, see [How to get user roles in a JSP / Servlet|https://stackoverflow.com/questions/344117/how-to-get-user-roles-...]. > That's about 100 roles for us. We were expecting that would be a lookup into a {{HashMap}} or similar with O(1) complexity and almost no allocations. > This however does not seem to be case as {{EJBContextImpl#isCallerInRole}} seems to do the role mapping for every call. This results in a large amount of allocations. In our case this completely dominates our allocation profile. See attached screenshot from JFR. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-12979?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFLY-12979. ------------------------------------- Resolution: Duplicate Issue > JWT signed by 1024 bit long key is rejected > ------------------------------------------- > > Key: WFLY-12979 > URL: https://issues.redhat.com/browse/WFLY-12979 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Major > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFLY-12980: --------------------------------------- Assignee: (was: Darran Lofthouse) > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Yeser Amer edited comment on DROOLS-4950 at 1/17/20 10:08 AM: -------------------------------------------------------------- [~jomarko] I tested it. In my opinion it's not a bug. The second row holds in GIVEN a List with [1,2,3]. In EXPECTED you put ?=[2], which is wrong. Change it to ?=[1, 2, 3] and it will work. Please double check it, and if you confirm it's not a bug please close it. Thanks was (Author: yamer): [~jomarko] I tested it. In my opinion it's not a bug. The second row holds in GIVEN a List with [1,2,3]. In EXPECTED you put ?=[2], which is wrong. Change it to ?=[1, 2, 3] and it will works. Please double check it, and if you confirm it's not a bug please close it. Thanks > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4950: ------------------------------------ [~jomarko] I tested it. In my opinion it's not a bug. The second row holds in GIVEN a List with [1,2,3]. In EXPECTED you put ?=[2], which is wrong. Change it to ?=[1, 2, 3] and it will works. Please double check it, and if you confirm it's not a bug please close it. Thanks > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4906) Maven configuration script is not able to start in HA-CEP image in Openshift

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4906?page=com.atlassian.jira.plug... ] Massimiliano Dessi resolved DROOLS-4906. ---------------------------------------- Resolution: Done > Maven configuration script is not able to start in HA-CEP image in Openshift > ---------------------------------------------------------------------------- > > Key: DROOLS-4906 > URL: https://issues.redhat.com/browse/DROOLS-4906 > Project: Drools > Issue Type: Bug > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Blocker > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4940) Create slides for Drools Deep Dive presentation in Japan

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4940?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4940. --------------------------------- Resolution: Done Done https://docs.google.com/presentation/d/1dz8-wWAezawFwDazJ4fIKqNWd_Qlwsdsf... > Create slides for Drools Deep Dive presentation in Japan > -------------------------------------------------------- > > Key: DROOLS-4940 > URL: https://issues.redhat.com/browse/DROOLS-4940 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12088) JAR does not supported for deployment-overlays mechanism

by Vlad Filipp (Jira)

[ https://issues.redhat.com/browse/WFLY-12088?page=com.atlassian.jira.plugi... ] Vlad Filipp commented on WFLY-12088: ------------------------------------ Hi [~baranowb]. There is not software bug. I trying to add overlay to WAR inside EAR, but documentation didn't mention this. After research and debugging, I changed the path to the right path in the content tag and it's fixed. > JAR does not supported for deployment-overlays mechanism > -------------------------------------------------------- > > Key: WFLY-12088 > URL: https://issues.redhat.com/browse/WFLY-12088 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 16.0.0.Final > Reporter: Vlad Filipp > Assignee: Bartosz Baranowski > Priority: Major > > When trying to make a link from an overlay to a JAR, classes from overlay libraries are not loaded for a linked JAR. > The situation is similar when creating a link to a JAR which is located inside EAR. > Should overlay deployment mechanism be supported for JARs? > Example standalone.xml: > {code:java} > <deployment-overlays> > ... > <deployment-overlay name="my-overlay-n1"> > <content ...> > <deployment name="my-jar-inside-ear-use-overlays-libs.jar"/> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12993) Upgrade Smallrye JWT to 2.0.12

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12993: --------------------------------------- Summary: Upgrade Smallrye JWT to 2.0.12 Key: WFLY-12993 URL: https://issues.redhat.com/browse/WFLY-12993 Project: WildFly Issue Type: Component Upgrade Components: MP JWT Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 19.0.0.Beta1 This is an upgrade to a private module used to provide JWT capabilities within WildFly. https://github.com/smallrye/smallrye-jwt/compare/2.0.11...2.0.12 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4951) Update docs about kjar, springboot, jdkhttp about id_user range

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4951?page=com.atlassian.jira.plug... ] Massimiliano Dessi commented on DROOLS-4951: -------------------------------------------- Every project ask a specific range to use for a user Minishift: "Error creating: pods "openshift-kie-springboot-545874cb7-" is forbidden: unable to validate against any security context constraint: [spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000170000, 1000179999]]" Openshift [spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000170000: must be in the ranges: [1000520000, 1000529999]]' the only way to find a correct value before is with *oc describe*: oc describe project test-9946 Name: test-9946 Created: 8 minutes ago Labels: <none> Annotations: openshift.io/description= openshift.io/display-name= openshift.io/requester=kube:admin openshift.io/sa.scc.mcs=s0:c24,c9 openshift.io/sa.scc.supplemental-groups=1000570000/10000 openshift.io/sa.scc.uid-range=1000570000/10000 Display Name: <none> Description: <none> Status: Active Node Selector: <none> Quota: <none> Resource limits: <none> with these values the user must change accordingly the value in the Dockerfile and in the deployment.yaml > Update docs about kjar, springboot, jdkhttp about id_user range > ---------------------------------------------------------------- > > Key: DROOLS-4951 > URL: https://issues.redhat.com/browse/DROOLS-4951 > Project: Drools > Issue Type: Enhancement > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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