May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-316) Different behaviour of ADMIN_PASSWORD and securing management interface

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFWIP-316?page=com.atlassian.jira.plugin... ] Martin Choma commented on WFWIP-316: ------------------------------------ I am experiencing same issue with same symptoms with XP CR1 images [1], thus raising priority to blocker. My main concern this behaviour is not consistent between legacy (7.3.1) and Elytron (XP) approach. If we conclude the discussion that one or another approach is correct we should unify it on both places XP and 7.3.1 in my opinion. [1] https://errata.devel.redhat.com/advisory/54279 > Different behaviour of ADMIN_PASSWORD and securing management interface > ----------------------------------------------------------------------- > > Key: WFWIP-316 > URL: https://issues.redhat.com/browse/WFWIP-316 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > With XP image started to fail test where {{ADMIN_PASSWORD}} env var is empty. Because test is expecting management interface to be unsecured in that case. But this does not happen and management interface is secured with SASL authentication factory. Test is using CLI so it is SASL which is used for accessing management interface. > Seems in other images CD, 7.3.0.GA (with legacy security in place) when {{ADMIN_PASSWORD}} was empty management interface was left unsecured. > Seems to me we should be consistent between legacy security and Elytron approach of securing OpenShift images. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2407) CompositeMessage: collapse into BytesMessage at the receiver

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2407?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2407. ---------------------------- Resolution: Done Added method {{CompositeMessage.collapse(boolean)}} > CompositeMessage: collapse into BytesMessage at the receiver > ------------------------------------------------------------ > > Key: JGRP-2407 > URL: https://issues.redhat.com/browse/JGRP-2407 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Beta1 > > > If a sender sends a CompositeMessage, say of an NioMessage of 500 bytes and a BytesMessage of 10 bytes, provide the option to unmarshal the message into a BytesMessage of 510 bytes at the receiver. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4954) Add legacy controller for EAP 7.3

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-4954?page=com.atlassian.jira.plug... ] Yeray Borges Santana updated WFCORE-4954: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-legacy-test/pull/10, https://github.com/wildfly/wildfly-core/pull/4195 (was: https://github.com/wildfly/wildfly-legacy-test/pull/10) Added PR link for step 2) > Add legacy controller for EAP 7.3 > --------------------------------- > > Key: WFCORE-4954 > URL: https://issues.redhat.com/browse/WFCORE-4954 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > > Add legacy controllers to test transformers against EAP 7.3.0. > There are two things to complete to get this task done: > # We need to add the EAP 7.3.0 controllers in https://github.com/wildfly/wildfly-legacy-test > # We need to upgrade the wildfly-legacy-test dependency and add the new versions to {{ModelTestControllerVersion}} and {{TransformersTestParameter}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13404) Upgrade Hibernate ORM from 5.3.16 to 5.3.17

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13404?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13404: ------------------------------------ Description: https://github.com/hibernate/hibernate-orm/compare/5.3.16...5.3.17 > Upgrade Hibernate ORM from 5.3.16 to 5.3.17 > ------------------------------------------- > > Key: WFLY-13404 > URL: https://issues.redhat.com/browse/WFLY-13404 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Gail Badner > Priority: Major > Fix For: 20.0.0.Beta1 > > > https://github.com/hibernate/hibernate-orm/compare/5.3.16...5.3.17 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13419) Upgrade hibernate-validator from 6.0.19 to 6.0.20

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13419?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13419: ------------------------------------ Security: (was: Red Hat Internal) > Upgrade hibernate-validator from 6.0.19 to 6.0.20 > ------------------------------------------------- > > Key: WFLY-13419 > URL: https://issues.redhat.com/browse/WFLY-13419 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate > Reporter: Ilia Vassilev > Assignee: Gail Badner > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > Tag: https://github.com/hibernate/hibernate-validator/releases/tag/6.0.20.Final > Diff: https://github.com/hibernate/hibernate-validator/compare/6.0.19.Final...6... > Commit hash: https://github.com/hibernate/hibernate-validator/commit/4dc4cd3779c829ca8... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13403) Upgrade Hibernate ORM from 5.3.16 to 5.3.17

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-13403?page=com.atlassian.jira.plugi... ] Ilia Vassilev closed WFLY-13403. -------------------------------- Resolution: Duplicate Issue Duplicate of WFLY-13404 > Upgrade Hibernate ORM from 5.3.16 to 5.3.17 > ------------------------------------------- > > Key: WFLY-13403 > URL: https://issues.redhat.com/browse/WFLY-13403 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate > Affects Versions: 19.0.0.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > This is intended for EAP 7.3.2. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13436) Refactor AbstractDeploymentUnitProcessor maybe remove it

by Cheng Fang (Jira)

Cheng Fang created WFLY-13436: --------------------------------- Summary: Refactor AbstractDeploymentUnitProcessor maybe remove it Key: WFLY-13436 URL: https://issues.redhat.com/browse/WFLY-13436 Project: WildFly Issue Type: Enhancement Components: EJB Reporter: Cheng Fang Assignee: Cheng Fang * {{AbstractDeploymentUnitProcessor}} is declared {{public}}, but is not used else where. * It has only 1 subclass, {{AnnotatedEJBComponentDescriptionDeploymentUnitProcessor}}. Need to check if we can remove {{AbstractDeploymentUnitProcessor}}. There are about 39 DUP classes in ejb3, and there could be some common logic that can be placed in a super class. Need to double check. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4959) Feature for checking module installation in JBoss

by Joao Paulo Goncalves (Jira)

[ https://issues.redhat.com/browse/WFCORE-4959?page=com.atlassian.jira.plug... ] Joao Paulo Goncalves commented on WFCORE-4959: ---------------------------------------------- Thanks for answering. I can't understand the new problem context because the idea I had about your idea is: The HC's are informed that there are new modules to download and they go there, download, and install them. Sorry if I can't see beyond. > Feature for checking module installation in JBoss > ------------------------------------------------- > > Key: WFCORE-4959 > URL: https://issues.redhat.com/browse/WFCORE-4959 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Joao Paulo Goncalves > Assignee: Brian Stansberry > Priority: Major > > Using CLI tool or Administrative Console is not possible at this moment to check if a custom added module was added correctly, especially in domain mode. The only alternative available is to add host per host. This approach takes time, and for unused users there isn't some visual (GUI) to help them. > JBoss CLI approach: > module --add --source=jar1,jar2 --target=/path-of-module --host=your-host OR module --add --source=jar1,jar2 --target=/path-of-module --host=all (deploy the module in all hosts that belongs to the domain) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ] Richard Achmatowicz edited comment on WFLY-13433 at 5/6/20 2:10 PM: -------------------------------------------------------------------- Introducing a central repository for capability names and references, as used in Undertow: {noformat} public final class Capabilities { /* * Capabilities defined in this subsystem */ public static final String CAPABILITY_APPLICATION_SECURITY_DOMAIN = "org.wildfly.ejb3.application-security-domain"; public static final String CAPABILITY_CLUSTERED_SINGLETON = "org.wildfly.ejb3.clustered.singleton"; public static final String CAPABILITY_EJB3 = "org.wildfly.ejb3"; public static final String CAPABILITY_EJB_REMOTE = "org.wildfly.ejb.remote"; public static final String CAPABILITY_IDENTITY = "org.wildfly.ejb3.identity"; public static final String CAPABILITY_REMOTE_CLIENT_CONFIGURATOR = "org.wildfly.ejb3.remote.client-configurator"; /* * Capabilities referenced by this subsystem */ public static final String REF_GLOBAL_DEFAULT_LOCAL_PROVIDER = "org.wildfly.transactions.global-default-local-provider"; public static final String REF_JACC_POLICY = "org.wildfly.security.jacc-policy"; public static final String REF_SECURITY_DOMAIN = "org.wildfly.security.security-domain"; public static final String REF_LEGACY_SERVER_SECURITY_MANAGER = "org.wildfly.legacy-security.server-security-manager"; public static final String REF_TXN_SYNCHRONIZATION_REGISTRY = "org.wildfly.transactions.transaction-synchronization-registry"; } {noformat} This will eliminate the many capability-related text strings being defined across the resources in EJB3 subsystem and give a better picture of what is defined and what is referenced. Had a chat with Paul and he mentioned that for capabilities in the top section which are not intended to be consumed by other subsystems, and just act to express dependencies, these strings should really be private (or at worst protected); in other words, not visible to the outside world. Most capabilities defined within EJB3 resources will not be consumed from outside, but a few may. was (Author: rachmato): Introducing a central repository for capability names and references, as used in Undertow: {noformat} public final class Capabilities { /* * Capabilities defined in this subsystem */ public static final String CAPABILITY_APPLICATION_SECURITY_DOMAIN = "org.wildfly.ejb3.application-security-domain"; public static final String CAPABILITY_CLUSTERED_SINGLETON = "org.wildfly.ejb3.clustered.singleton"; public static final String CAPABILITY_EJB3 = "org.wildfly.ejb3"; public static final String CAPABILITY_EJB_REMOTE = "org.wildfly.ejb.remote"; public static final String CAPABILITY_IDENTITY = "org.wildfly.ejb3.identity"; public static final String CAPABILITY_REMOTE_CLIENT_CONFIGURATOR = "org.wildfly.ejb3.remote.client-configurator"; /* * Capabilities referenced by this subsystem */ public static final String REF_GLOBAL_DEFAULT_LOCAL_PROVIDER = "org.wildfly.transactions.global-default-local-provider"; public static final String REF_JACC_POLICY = "org.wildfly.security.jacc-policy"; public static final String REF_SECURITY_DOMAIN = "org.wildfly.security.security-domain"; public static final String REF_LEGACY_SERVER_SECURITY_MANAGER = "org.wildfly.legacy-security.server-security-manager"; public static final String REF_TXN_SYNCHRONIZATION_REGISTRY = "org.wildfly.transactions.transaction-synchronization-registry"; } {noformat} This will eliminate the many capability-related text strings being defined across the resources in EJB3 subsystem and give a better picture of what is defined and what is referenced. > Improve capability support in EJB3 subsystem > -------------------------------------------- > > Key: WFLY-13433 > URL: https://issues.redhat.com/browse/WFLY-13433 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 20.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > > Survey all external subsystem dependencies and introduce capability based dependencies where required. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4954) Add legacy controller for EAP 7.3

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-4954?page=com.atlassian.jira.plug... ] Yeray Borges Santana updated WFCORE-4954: ----------------------------------------- Description: Add legacy controllers to test transformers against EAP 7.3.0. There are two things to complete to get this task done: # We need to add the EAP 7.3.0 controllers in https://github.com/wildfly/wildfly-legacy-test # We need to upgrade the wildfly-legacy-test dependency and add the new versions to {{ModelTestControllerVersion}} and {{TransformersTestParameter}} was:Add legacy controllers to test transformers against EAP 7.3.0 > Add legacy controller for EAP 7.3 > --------------------------------- > > Key: WFCORE-4954 > URL: https://issues.redhat.com/browse/WFCORE-4954 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > > Add legacy controllers to test transformers against EAP 7.3.0. > There are two things to complete to get this task done: > # We need to add the EAP 7.3.0 controllers in https://github.com/wildfly/wildfly-legacy-test > # We need to upgrade the wildfly-legacy-test dependency and add the new versions to {{ModelTestControllerVersion}} and {{TransformersTestParameter}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 2020