January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2153) Encrypt protocols transform empty buffer into null buffer when encrypt_entire_message is disabled

by Paul Ferraro (JIRA)

Paul Ferraro created JGRP-2153: ---------------------------------- Summary: Encrypt protocols transform empty buffer into null buffer when encrypt_entire_message is disabled Key: JGRP-2153 URL: https://issues.jboss.org/browse/JGRP-2153 Project: JGroups Issue Type: Bug Affects Versions: 3.6.12 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 4.0, 3.6.13 This causes an NPEs in WildFly where empty buffers have significance (i.e. to indicate an unknown fork channel). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-5) Initial setup for the build infrastructure

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-5?page=com.atlassian.jira.plugin.syste... ] Luis Barreiro resolved AG-5. ---------------------------- Fix Version/s: 0.0.1 Resolution: Done Maven to be used as build tool. For consistency (and convenience) project depends on jboss-parent > Initial setup for the build infrastructure > ------------------------------------------ > > Key: AG-5 > URL: https://issues.jboss.org/browse/AG-5 > Project: Agroal > Issue Type: Task > Components: build > Affects Versions: 0.0.0 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.0.1 > > > Choose a build tool and do it's initial setup -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2223) Setting JBOSS_MODULEPATH is lost for second start of embed-server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2223?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2223: ------------------------------------------ See "Modular vs Non-Modular Classloading and JBOSS_HOME" in http://wildfly.org/news/2015/03/13/Offline-CLI/ re module loading. Basically if you run the CLI as a modular application, the module path is what was used to set up the CLI process, and if you use jboss-cli.sh it supports JBOSS_MODULE_PATH. If you do not run the CLI as a modular app, then the module path is <value_of_jboss_home>/modules and JBOSS_MODULE_PATH has no meaning. The simple thing to do here is to remove the validation of the property value. The property is deprecated and has had no meaning for many years; all it does is drive the value of a deprecated runtime management attribute that we preserve for management API compatibility. There's no reason to validate this value. > Setting JBOSS_MODULEPATH is lost for second start of embed-server > ----------------------------------------------------------------- > > Key: WFCORE-2223 > URL: https://issues.jboss.org/browse/WFCORE-2223 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Server > Reporter: Josef Cacek > Assignee: Brian Stansberry > Priority: Critical > > When {{embed-server}} command is used more times in the CLI and a custom {{JBOSS_MODULEPATH}} is configured, then only the first server start uses the correct module path. > The subsequent `embed-server` call results in error: > {code} > Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0118: Determined modules directory does not exist: /tmp/jboss-eap-7.0-no-modules/modules > {code} > Using the {{JBOSS_MODULEPATH}} environment variable is documented in https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1802) Integrate OpenSSL Provider registration with Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1802: ------------------------------------------ I am undecided ;-) The Elytron Subsystem now discovers and registers the Provider so we should be able to remove it from the current location. We probably should encourage the use of the Elytron subsystem for SSLContext definitions and both Elytron and the OpenSSL integration are new in WildFly 11. BUT attempting to use the OpenSSL provider in legacy resources could then become racey as the legacy services don't depend on the core Elytron services by default. > Integrate OpenSSL Provider registration with Elytron > ---------------------------------------------------- > > Key: WFCORE-1802 > URL: https://issues.jboss.org/browse/WFCORE-1802 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Stuart Douglas > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Alpha23 > > > We need to remove the following block from SecurityRealmResourceDefinition: - > {code} > static { > //register the Openssl Provider, if possible > //not really sure if this is the best place for it > try { > OpenSSLProvider.register(); > DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider(); > } catch (Throwable t){ > DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider"); > } > } > {code} > Registration will then be possible within the Elytron subsystem configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1802) Integrate OpenSSL Provider registration with Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1802: ------------------------------------- Priority: Blocker (was: Major) > Integrate OpenSSL Provider registration with Elytron > ---------------------------------------------------- > > Key: WFCORE-1802 > URL: https://issues.jboss.org/browse/WFCORE-1802 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Stuart Douglas > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Alpha23 > > > We need to remove the following block from SecurityRealmResourceDefinition: - > {code} > static { > //register the Openssl Provider, if possible > //not really sure if this is the best place for it > try { > OpenSSLProvider.register(); > DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider(); > } catch (Throwable t){ > DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider"); > } > } > {code} > Registration will then be possible within the Elytron subsystem configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1802) Integrate OpenSSL Provider registration with Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1802: ------------------------------------- Fix Version/s: 3.0.0.Alpha23 (was: 4.0.0.Beta1) > Integrate OpenSSL Provider registration with Elytron > ---------------------------------------------------- > > Key: WFCORE-1802 > URL: https://issues.jboss.org/browse/WFCORE-1802 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Stuart Douglas > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha23 > > > We need to remove the following block from SecurityRealmResourceDefinition: - > {code} > static { > //register the Openssl Provider, if possible > //not really sure if this is the best place for it > try { > OpenSSLProvider.register(); > DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider(); > } catch (Throwable t){ > DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider"); > } > } > {code} > Registration will then be possible within the Elytron subsystem configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1802) Integrate OpenSSL Provider registration with Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1802: ------------------------------------- Fix Version/s: 4.0.0.Beta1 (was: 3.0.0.Alpha23) > Integrate OpenSSL Provider registration with Elytron > ---------------------------------------------------- > > Key: WFCORE-1802 > URL: https://issues.jboss.org/browse/WFCORE-1802 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Stuart Douglas > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 4.0.0.Beta1 > > > We need to remove the following block from SecurityRealmResourceDefinition: - > {code} > static { > //register the Openssl Provider, if possible > //not really sure if this is the best place for it > try { > OpenSSLProvider.register(); > DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider(); > } catch (Throwable t){ > DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider"); > } > } > {code} > Registration will then be possible within the Elytron subsystem configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1802) Integrate OpenSSL Provider registration with Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1802: ------------------------------------- Priority: Major (was: Blocker) > Integrate OpenSSL Provider registration with Elytron > ---------------------------------------------------- > > Key: WFCORE-1802 > URL: https://issues.jboss.org/browse/WFCORE-1802 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Stuart Douglas > Assignee: Darran Lofthouse > Fix For: 4.0.0.Beta1 > > > We need to remove the following block from SecurityRealmResourceDefinition: - > {code} > static { > //register the Openssl Provider, if possible > //not really sure if this is the best place for it > try { > OpenSSLProvider.register(); > DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider(); > } catch (Throwable t){ > DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider"); > } > } > {code} > Registration will then be possible within the Elytron subsystem configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7123) Use elytron ssl-context for undertow default https listener

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7123?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-7123. ------------------------------------ Resolution: Rejected Default configuration will remain referencing legacy configuration. > Use elytron ssl-context for undertow default https listener > ----------------------------------------------------------- > > Key: WFLY-7123 > URL: https://issues.jboss.org/browse/WFLY-7123 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > Default undertow https listener use legacy ssl context in standalone-elytron.xml . > {code} > <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/> > {code} > Once elytron becomes default security solution in wildfly it has to use elytron ssl context. In meantime prepare such configuration in standalone-elytron.xml > {code} > <https-listener name="https" socket-binding="https" ssl-context="elytron-ssl-context" enable-http2="true"/> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7697) Update default Elytron backed configuration to use Elytron role mapping instead of management role mapping.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7697?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-7697. ------------------------------------ Resolution: Rejected We no longer have a default management definition backed by Elytron. > Update default Elytron backed configuration to use Elytron role mapping instead of management role mapping. > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-7697 > URL: https://issues.jboss.org/browse/WFLY-7697 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017