February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (ELY-2079) (7.3.z) ELY-2069 - JWT token validation uses int instead of long for the dates: exp (expiration) and nbf

by Ilia Vassilev (Jira)

Ilia Vassilev created ELY-2079: ---------------------------------- Summary: (7.3.z) ELY-2069 - JWT token validation uses int instead of long for the dates: exp (expiration) and nbf Key: ELY-2079 URL: https://issues.redhat.com/browse/ELY-2079 Project: WildFly Elytron Issue Type: Bug Components: Realms Affects Versions: 1.14.1.Final Reporter: Ilia Vassilev Assignee: Ilia Vassilev Fix For: 1.15.0.CR1 JwtValidator is reading the exp and nbf field as a Java int instead of long: [https://github.com/wildfly-security/wildfly-elytron/blob/master/auth/real...] This means the maximum expiration date is ~January 18, 2038. Also, with Javascript a NumericDate this would be a 64-bit value. The JWT spec also leaves open the possibility of a decimal value so that should possibly be accounted for. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14386) SecurityBootstrapService should set TCCL before calling PolicyConfigurationFactory.getPolicyConfigurationFactory()

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14386: --------------------------------------- Summary: SecurityBootstrapService should set TCCL before calling PolicyConfigurationFactory.getPolicyConfigurationFactory() Key: WFLY-14386 URL: https://issues.redhat.com/browse/WFLY-14386 Project: WildFly Issue Type: Bug Components: Security Reporter: Brian Stansberry Assignee: Darran Lofthouse This: https://github.com/wildfly/wildfly/blob/22.0.0.Final/security/subsystem/s... should be more like this: https://github.com/wildfly/wildfly/blob/22.0.0.Final/ee/src/main/java/org... They both deal with the 'org.jboss.as.security.jacc-module' but one sets the TCCL to its module and the other does not. SecurityBootstrapService not doing that means the module, if defined, has to be a dependency of the org.jboss.as.security module. Such a module would be custom, meaning the user is editing our module.xml, and we don't want that. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14385) Ensure wildfly-clustering-server ProtoStream marshallers use valid protobuf encoding

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-14385: ----------------------------------- Summary: Ensure wildfly-clustering-server ProtoStream marshallers use valid protobuf encoding Key: WFLY-14385 URL: https://issues.redhat.com/browse/WFLY-14385 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 22.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Most ProtoStream marshallers in wildfly-clustering-server are adapted from Externalizers, and thus do not use valid protobuf encoding. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2527) NPE if binding JGroups to an IP without interface

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/JGRP-2527?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated JGRP-2527: ------------------------------ Affects Version/s: 4.2.9 > NPE if binding JGroups to an IP without interface > ------------------------------------------------- > > Key: JGRP-2527 > URL: https://issues.redhat.com/browse/JGRP-2527 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.9 > Reporter: Pedro Ruivo > Assignee: Bela Ban > Priority: Minor > > If you bind JGroups to 127.0.2.1 (or any IP without an interface, like 127.0.0.0/8 - loopback IP addresses (refers to self) RFC 5735), JGroups fails with an NPE: > {noformat} > Caused by: java.lang.NullPointerException > at org.jgroups.protocols.UDP.dumpSocketInfo(UDP.java:558) > at org.jgroups.protocols.UDP.createSockets(UDP.java:422) > at org.jgroups.protocols.UDP.start(UDP.java:292) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:868) > at org.jgroups.JChannel.startStack(JChannel.java:980) > at org.jgroups.JChannel._preConnect(JChannel.java:844) > at org.jgroups.JChannel.connect(JChannel.java:349) > at org.jgroups.JChannel.connect(JChannel.java:343) > {noformat} > The exception comes from this line: [https://github.com/belaban/JGroups/blob/4.x/src/org/jgroups/protocols/UDP...] > {{NetworkInterface.getByInetAddress(bind_addr)}} returns {{null}} since the IP does not have an interface. It would be nice to have a null check here to prevent the NPE. > This is useful for local testing when `port_range=0`. It allows having a dedicated IP for each JGroups instance. > Workaround: > The workaround requires you to create a virtual interface > {noformat} > sudo ifconfig lo:0 127.0.2.1 up > {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2527) NPE if binding JGroups to an IP without interface

by Pedro Ruivo (Jira)

Pedro Ruivo created JGRP-2527: --------------------------------- Summary: NPE if binding JGroups to an IP without interface Key: JGRP-2527 URL: https://issues.redhat.com/browse/JGRP-2527 Project: JGroups Issue Type: Bug Reporter: Pedro Ruivo Assignee: Bela Ban If you bind JGroups to 127.0.2.1 (or any IP without an interface, like 127.0.0.0/8 - loopback IP addresses (refers to self) RFC 5735), JGroups fails with an NPE: {noformat} Caused by: java.lang.NullPointerException at org.jgroups.protocols.UDP.dumpSocketInfo(UDP.java:558) at org.jgroups.protocols.UDP.createSockets(UDP.java:422) at org.jgroups.protocols.UDP.start(UDP.java:292) at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:868) at org.jgroups.JChannel.startStack(JChannel.java:980) at org.jgroups.JChannel._preConnect(JChannel.java:844) at org.jgroups.JChannel.connect(JChannel.java:349) at org.jgroups.JChannel.connect(JChannel.java:343) {noformat} The exception comes from this line: [https://github.com/belaban/JGroups/blob/4.x/src/org/jgroups/protocols/UDP...] {{NetworkInterface.getByInetAddress(bind_addr)}} returns {{null}} since the IP does not have an interface. It would be nice to have a null check here to prevent the NPE. This is useful for local testing when `port_range=0`. It allows having a dedicated IP for each JGroups instance. Workaround: The workaround requires you to create a virtual interface {noformat} sudo ifconfig lo:0 127.0.2.1 up {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5917) Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5917?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5917: --------------------------------- Priority: Minor (was: Major) > Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-5917 > URL: https://issues.redhat.com/browse/DROOLS-5917 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Minor > > It should be possible to put the actual constraints in comments in a generated ANC by leveraging the `PredicateInformation` class used in the executable model to give better error messages. > In the compiled alpha network, instead of > private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=Constraint for '0066e054-7241-4ccd-886d-ab6d7e08a99e' (index: null)] > we should have > private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=x == true" (index: null)] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5917) Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5917?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5917: --------------------------------- Issue Type: Enhancement (was: Bug) > Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-5917 > URL: https://issues.redhat.com/browse/DROOLS-5917 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > It should be possible to put the actual constraints in comments in a generated ANC by leveraging the `PredicateInformation` class used in the executable model to give better error messages. > In the compiled alpha network, instead of > private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=Constraint for '0066e054-7241-4ccd-886d-ab6d7e08a99e' (index: null)] > we should have > private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=x == true" (index: null)] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5984: --------------------------------- Issue Type: Enhancement (was: Feature Request) > DMN Alpha Network - Range Indexing > ---------------------------------- > > Key: DROOLS-5984 > URL: https://issues.redhat.com/browse/DROOLS-5984 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Minor > > Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. > Also we would need to change range index threshold to test easier). -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5984: --------------------------------- Priority: Minor (was: Major) > DMN Alpha Network - Range Indexing > ---------------------------------- > > Key: DROOLS-5984 > URL: https://issues.redhat.com/browse/DROOLS-5984 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Minor > > Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. > Also we would need to change range index threshold to test easier). -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5984: --------------------------------- Issue Type: Feature Request (was: Bug) > DMN Alpha Network - Range Indexing > ---------------------------------- > > Key: DROOLS-5984 > URL: https://issues.redhat.com/browse/DROOLS-5984 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Minor > > Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. > Also we would need to change range index threshold to test easier). -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 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 February 2021