December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-845) Coverity: dereference null value in ClassLoadingAttributeDefinitions (Elytron subsystem)

by Josef Cacek (JIRA)

Josef Cacek created ELY-845: ------------------------------- Summary: Coverity: dereference null value in ClassLoadingAttributeDefinitions (Elytron subsystem) Key: ELY-845 URL: https://issues.jboss.org/browse/ELY-845 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Coverity static-analysis scan found a possilbe method call on null object in the {{ClassLoadingAttributeDefinitions.resolveClassLoader}} method. https://scan7.coverity.com/reports.htm#v16159/p12663/fileInstanceId=68921... Following code {code:java} Module current = Module.getCallerModule(); if (module != null) { ModuleIdentifier mi = ModuleIdentifier.fromString(module); current = current.getModule(mi); {code} The {{current}} value returned from {{Module.getCallerModule()}} may be {{null}}. The {{getModule()}} method is called on it without the null-check. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2125) Undertow 1.4.8.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-2125: ----------------------------------- Summary: Undertow 1.4.8.Final Key: WFCORE-2125 URL: https://issues.jboss.org/browse/WFCORE-2125 Project: WildFly Core Issue Type: Component Upgrade Reporter: Jeff Mesnil Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2124) Undertow 1.4.8.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2124?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFCORE-2124: ----------------------------------- Assignee: Stuart Douglas > Undertow 1.4.8.Final > -------------------- > > Key: WFCORE-2124 > URL: https://issues.jboss.org/browse/WFCORE-2124 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Jeff Mesnil > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2124) Undertow 1.4.8.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-2124: ----------------------------------- Summary: Undertow 1.4.8.Final Key: WFCORE-2124 URL: https://issues.jboss.org/browse/WFCORE-2124 Project: WildFly Core Issue Type: Component Upgrade Reporter: Jeff Mesnil -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7810) Artemis hangs during failback in remote JCA scenario

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7810?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-7928 to WFLY-7810: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7810 (was: JBEAP-7928) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) Affects Version/s: (was: 7.0.3.GA) (was: 7.1.0.DR9) > Artemis hangs during failback in remote JCA scenario > ---------------------------------------------------- > > Key: WFLY-7810 > URL: https://issues.jboss.org/browse/WFLY-7810 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > > Remote JCA scenario: > * There are 3 nodes > * Node 1 and node 2 are Live-Backup pair (replicated HA) > * Node 3 has MDB which remotely connects to node 1 and is able to do failover on node 2 > * During the test, node 1 is killed and started again > Problem occurs when node 1 is started again. Servers are configured to do failback. When node 1 wants to become live again, something goes wrong with connection between node 1 and node 2. On node 1 I can see repeated WARN message \[1\]. Node 2 prints repeatedly WARN message \[2\]. > I can see the same issue also with 7.0.x. We haven't notice this error because the test didn't check state of servers after the failback. > When I modify the test to not deploy MDB on node 3, the test passes without any unusual error. It seems the issue is related to this scenario. > \[1\] > {code} > 09:59:09,197 WARN [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@26357508-1826618556)) AMQ222137: Unable to announce backup, retrying: ActiveMQConnec > tionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119012: Timed out waiting to receive initial broadcast from cluster] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:747) [artemis-core-client-1.5.0.redhat-1.jar:1.5.0.redhat-1] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:625) [artemis-core-client-1.5.0.redhat-1.jar:1.5.0.redhat-1] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:607) [artemis-core-client-1.5.0.redhat-1.jar:1.5.0.redhat-1] > at org.apache.activemq.artemis.core.server.cluster.BackupManager$BackupConnector$1.run(BackupManager.java:246) [artemis-server-1.5.0.redhat-1.jar:1.5.0.redhat-1] > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:101) [artemis-commons-1.5.0.redhat-1.jar:1.5.0.redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_111] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_111] > {code} > \[2\] > {code} > 10:00:19,245 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:00:29,245 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:00:39,245 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:00:49,246 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:00:59,247 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:01:09,247 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:01:19,248 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:01:29,248 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:01:39,249 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:01:49,249 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:01:59,250 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > 10:02:09,250 WARN [org.apache.activemq.artemis.core.client] (Thread-135) AMQ212042: Timed out waiting for packet to be flushed > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-844) Coverity: default platform encoding used in TokenRealmDefinition (Elytron subsystem)

by Josef Cacek (JIRA)

Josef Cacek created ELY-844: ------------------------------- Summary: Coverity: default platform encoding used in TokenRealmDefinition (Elytron subsystem) Key: ELY-844 URL: https://issues.jboss.org/browse/ELY-844 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Minor Coverity static-analysis scan found a String to byte conversion with default platform encoding in the {{TokenRealmDefinition.performRuntime}} method. https://scan7.coverity.com/reports.htm#v16159/p12663/fileInstanceId=68921... Following code {code:java} jwtValidatorBuilder.publicKey(publicKey.getBytes()); {code} The encoding should be specified as argument. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7499) Elytron "expressions-allowed" => false attributes

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7499?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-7499 at 12/16/16 8:16 AM: ------------------------------------------------------------ Following are not reasonable to allow expressions, as they are referencing services: * /jdbc-realm/principal-query/data-source * /security-domain/default-realm * /credential-reference/store As well as any CredentialReference attribute. was (Author: honza889): Following are not reasonable to allow expressions, as they are referencing services: * /jdbc-realm/principal-query/data-source * /security-domain/default-realm * /credential-reference/store > Elytron "expressions-allowed" => false attributes > ------------------------------------------------- > > Key: WFLY-7499 > URL: https://issues.jboss.org/browse/WFLY-7499 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: user_experience > > Please change these attributes to {{"expressions-allowed" => true}} if reasonable > {code} > /configurable-sasl-server-factory/protocol > /configurable-sasl-server-factory/server-name > /filesystem-realm/levels > /token-realm/public-key > /token-realm/principal-claim > /token-realm/oauth2-introspection/host-name-verification-policy > /token-realm/oauth2-introspection/introspection-url > /token-realm/oauth2-introspection/client-secret > /token-realm/oauth2-introspection/client-id > /token-realm/oauth2-introspection/public-key > /token-realm/oauth2-introspection/token-realm > /jdbc-realm/principal-query/sql > /jdbc-realm/principal-query/data-source > /jdbc-realm/clear-password-mapper/password-index > /jdbc-realm/bcrypt-mapper/password-index > /jdbc-realm/bcrypt-mapper/salt-index > /jdbc-realm/bcrypt-mapper/iteration-count-index > /jdbc-realm/salted-simple-digest-mapper/algorithm > /jdbc-realm/salted-simple-digest-mapper/password-index > /jdbc-realm/salted-simple-digest-mapper/salt-index > /jdbc-realm/simple-digest-mapper/password-index > /jdbc-realm/scram-mapper/algorithm > /jdbc-realm/scram-mapper/password-index > /jdbc-realm/scram-mapper/salt-index > /jdbc-realm/scram-mapper/iteration-count-index > /security-domain/default-realm > These applies to key-store and key-manager: > */credential-reference/store > */credential-reference/alias > */credential-reference/type > */credential-reference/clear-text > {code} > These are not marked as capability reference. But seems referencing another service, so not sure if it is issue in these cases: > * /jdbc-realm/principal-query/data-source > * /security-domain/default-realm > * /credential-reference/store > "Collection of primitives" , e.g. LIST of STRING, OBJECT of STRING : > {code} > /configurable-sasl-server-factory/properties > /custom-role-mapper/configuration > /mapped-regex-realm-mapper/realm-map > /x500-attribute-principal-decoder/required-oids > /custom-permission-mapper/configuration > /configurable-http-server-mechanism-factory/properties > /custom-name-rewriter/configuration > /custom-principal-decoder/configuration > /custom-realm-mapper/configuration > /custom-modifiable-realm/configuration > /custom-credential-security-factory/configuration > /custom-role-decoder/configuration > /custom-realm/configuration > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7499) Elytron "expressions-allowed" => false attributes

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7499?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7499: ---------------------------------- Following are not reasonable to allow expressions, as they are referencing services: * /jdbc-realm/principal-query/data-source * /security-domain/default-realm * /credential-reference/store > Elytron "expressions-allowed" => false attributes > ------------------------------------------------- > > Key: WFLY-7499 > URL: https://issues.jboss.org/browse/WFLY-7499 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: user_experience > > Please change these attributes to {{"expressions-allowed" => true}} if reasonable > {code} > /configurable-sasl-server-factory/protocol > /configurable-sasl-server-factory/server-name > /filesystem-realm/levels > /token-realm/public-key > /token-realm/principal-claim > /token-realm/oauth2-introspection/host-name-verification-policy > /token-realm/oauth2-introspection/introspection-url > /token-realm/oauth2-introspection/client-secret > /token-realm/oauth2-introspection/client-id > /token-realm/oauth2-introspection/public-key > /token-realm/oauth2-introspection/token-realm > /jdbc-realm/principal-query/sql > /jdbc-realm/principal-query/data-source > /jdbc-realm/clear-password-mapper/password-index > /jdbc-realm/bcrypt-mapper/password-index > /jdbc-realm/bcrypt-mapper/salt-index > /jdbc-realm/bcrypt-mapper/iteration-count-index > /jdbc-realm/salted-simple-digest-mapper/algorithm > /jdbc-realm/salted-simple-digest-mapper/password-index > /jdbc-realm/salted-simple-digest-mapper/salt-index > /jdbc-realm/simple-digest-mapper/password-index > /jdbc-realm/scram-mapper/algorithm > /jdbc-realm/scram-mapper/password-index > /jdbc-realm/scram-mapper/salt-index > /jdbc-realm/scram-mapper/iteration-count-index > /security-domain/default-realm > These applies to key-store and key-manager: > */credential-reference/store > */credential-reference/alias > */credential-reference/type > */credential-reference/clear-text > {code} > These are not marked as capability reference. But seems referencing another service, so not sure if it is issue in these cases: > * /jdbc-realm/principal-query/data-source > * /security-domain/default-realm > * /credential-reference/store > "Collection of primitives" , e.g. LIST of STRING, OBJECT of STRING : > {code} > /configurable-sasl-server-factory/properties > /custom-role-mapper/configuration > /mapped-regex-realm-mapper/realm-map > /x500-attribute-principal-decoder/required-oids > /custom-permission-mapper/configuration > /configurable-http-server-mechanism-factory/properties > /custom-name-rewriter/configuration > /custom-principal-decoder/configuration > /custom-realm-mapper/configuration > /custom-modifiable-realm/configuration > /custom-credential-security-factory/configuration > /custom-role-decoder/configuration > /custom-realm/configuration > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-843) Coverity: Logically dead code in PermissionMapperDefinitions (Elytron subsystem)

by Josef Cacek (JIRA)

Josef Cacek created ELY-843: ------------------------------- Summary: Coverity: Logically dead code in PermissionMapperDefinitions (Elytron subsystem) Key: ELY-843 URL: https://issues.jboss.org/browse/ELY-843 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Coverity static-analysis scan found a logically dead code in the {{PermissionMapperDefinitions.getSimplePermissionMapper}} method. https://scan7.coverity.com/reports.htm#v16159/p12663/fileInstanceId=68921... https://scan7.coverity.com/reports.htm#v16159/p12663/fileInstanceId=68921... Following code {code:java} permissionMappings.add(new Mapping(principals != null ? principals : Collections.emptySet(), roles != null ? roles : Collections.emptySet(), permissions)); {code} should rather be {code:java} permissionMappings.add(new Mapping(principals, roles, permissions)); {code} because both {{principals}} and {{roles}} local variables are initialized ({{new HashSet...}}) before this piece of code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-842) Coverity: wrong condition in ProviderLoaderService.unregisterProviders (Elytron subsystem)

by Josef Cacek (JIRA)

Josef Cacek created ELY-842: ------------------------------- Summary: Coverity: wrong condition in ProviderLoaderService.unregisterProviders (Elytron subsystem) Key: ELY-842 URL: https://issues.jboss.org/browse/ELY-842 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Critical Coverity static-analysis scan found an issue in a loop within the {{ProviderLoaderService.unregisterProviders}} method. https://scan7.coverity.com/reports.htm#v16159/p12663/fileInstanceId=68921... The condition is wrong in the code {code:java} for (int i = providers.length - 1; i < 0; i--) { Security.removeProvider(providers[i].getName()); } {code} There should be {{i >= 0}} instead of {{i < 0}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 2016