June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6745) Support for SSL out of the box

by Erick de Oliveira Leal (JIRA)

[ https://issues.jboss.org/browse/WFLY-6745?page=com.atlassian.jira.plugin.... ] Erick de Oliveira Leal commented on WFLY-6745: ---------------------------------------------- https://issues.jboss.org/browse/WFLY-1598 duplicate of this right? > Support for SSL out of the box > ------------------------------ > > Key: WFLY-6745 > URL: https://issues.jboss.org/browse/WFLY-6745 > Project: WildFly > Issue Type: Feature Request > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.

by Erick de Oliveira Leal (JIRA)

[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ] Erick de Oliveira Leal commented on WFLY-1598: ---------------------------------------------- It was resolved here: https://issues.jboss.org/browse/WFLY-6745 right? > Out of the box SSL - or shortly after. > -------------------------------------- > > Key: WFLY-1598 > URL: https://issues.jboss.org/browse/WFLY-1598 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security,, management_sso > Fix For: 11.0.0.Alpha1 > > > There are various reasons that we do not support SSL/TLS out of the box e.g. > - If we ship a default keystore then everyone has access to the private key. > - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead. > This issue is to explorer other options to encourage their use and make it easier to configure. > As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-6781. -------------------------------- Resolution: Duplicate Issue Duplicates WFLY-6762. > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Paul Ferraro > Priority: Blocker > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6782) Unable to add JGroups protocol at a given index via CLI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6782?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6782: -------------------------------------- https://github.com/wildfly/wildfly/commit/72df91913de85b376d0c5d1c4d8e23c... > Unable to add JGroups protocol at a given index via CLI > ------------------------------------------------------- > > Key: WFLY-6782 > URL: https://issues.jboss.org/browse/WFLY-6782 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.1.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.Final > > > Unable to use this via CLI, tests pass since they use management client which won't check against the operation description: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(add-index=4) > 'add-index' is not found among the supported properties: [socket-binding, module, properties, type] > {noformat} > add index is missing in the description, after the fix: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=MPING:read-operation-description(name=add > { > "outcome" => "success", > "result" => { > "operation-name" => "add", > "description" => "Add a protocol to a protocol stack.", > "request-properties" => { > "add-index" => { > "type" => INT, > "description" => "If specified inserts the protocol at the given (zero-based) index. If null it will add at the end.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true > }, > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6783) Unable to add JGroups protocol at a given index via CLI

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-6783: ------------------------------------ Summary: Unable to add JGroups protocol at a given index via CLI Key: WFLY-6783 URL: https://issues.jboss.org/browse/WFLY-6783 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 8.2.1.Final, 9.0.2.Final, 10.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 10.1.0.Final Unable to use this via CLI, tests pass since they use management client which won't check against the operation description: {noformat} [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(add-index=4) 'add-index' is not found among the supported properties: [socket-binding, module, properties, type] {noformat} add index is missing in the description, after the fix: {noformat} [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=MPING:read-operation-description(name=add { "outcome" => "success", "result" => { "operation-name" => "add", "description" => "Add a protocol to a protocol stack.", "request-properties" => { "add-index" => { "type" => INT, "description" => "If specified inserts the protocol at the given (zero-based) index. If null it will add at the end.", "expressions-allowed" => false, "required" => false, "nillable" => true }, {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6782) Unable to add JGroups protocol at a given index via CLI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6782?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6782: --------------------------------- Affects Version/s: 10.0.0.Final 9.0.2.Final 8.2.1.Final > Unable to add JGroups protocol at a given index via CLI > ------------------------------------------------------- > > Key: WFLY-6782 > URL: https://issues.jboss.org/browse/WFLY-6782 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.1.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.Final > > > Unable to use this via CLI, tests pass since they use management client which won't check against the operation description: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(add-index=4) > 'add-index' is not found among the supported properties: [socket-binding, module, properties, type] > {noformat} > add index is missing in the description, after the fix: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=MPING:read-operation-description(name=add > { > "outcome" => "success", > "result" => { > "operation-name" => "add", > "description" => "Add a protocol to a protocol stack.", > "request-properties" => { > "add-index" => { > "type" => INT, > "description" => "If specified inserts the protocol at the given (zero-based) index. If null it will add at the end.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true > }, > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6782) Unable to add JGroups protocol at a given index via CLI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6782?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6782: --------------------------------- Fix Version/s: 10.1.0.Final > Unable to add JGroups protocol at a given index via CLI > ------------------------------------------------------- > > Key: WFLY-6782 > URL: https://issues.jboss.org/browse/WFLY-6782 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.2.1.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.Final > > > Unable to use this via CLI, tests pass since they use management client which won't check against the operation description: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(add-index=4) > 'add-index' is not found among the supported properties: [socket-binding, module, properties, type] > {noformat} > add index is missing in the description, after the fix: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=MPING:read-operation-description(name=add > { > "outcome" => "success", > "result" => { > "operation-name" => "add", > "description" => "Add a protocol to a protocol stack.", > "request-properties" => { > "add-index" => { > "type" => INT, > "description" => "If specified inserts the protocol at the given (zero-based) index. If null it will add at the end.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true > }, > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6782) Unable to add JGroups protocol at a given index via CLI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6782?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6782: --------------------------------- Description: Unable to use this via CLI, tests pass since they use management client which won't check against the operation description: {noformat} [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(add-index=4) 'add-index' is not found among the supported properties: [socket-binding, module, properties, type] {noformat} add index is missing in the description, after the fix: {noformat} [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=MPING:read-operation-description(name=add { "outcome" => "success", "result" => { "operation-name" => "add", "description" => "Add a protocol to a protocol stack.", "request-properties" => { "add-index" => { "type" => INT, "description" => "If specified inserts the protocol at the given (zero-based) index. If null it will add at the end.", "expressions-allowed" => false, "required" => false, "nillable" => true }, {noformat} > Unable to add JGroups protocol at a given index via CLI > ------------------------------------------------------- > > Key: WFLY-6782 > URL: https://issues.jboss.org/browse/WFLY-6782 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Unable to use this via CLI, tests pass since they use management client which won't check against the operation description: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(add-index=4) > 'add-index' is not found among the supported properties: [socket-binding, module, properties, type] > {noformat} > add index is missing in the description, after the fix: > {noformat} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=MPING:read-operation-description(name=add > { > "outcome" => "success", > "result" => { > "operation-name" => "add", > "description" => "Add a protocol to a protocol stack.", > "request-properties" => { > "add-index" => { > "type" => INT, > "description" => "If specified inserts the protocol at the given (zero-based) index. If null it will add at the end.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true > }, > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6782) Unable to add JGroups protocol at a given index via CLI

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-6782: ------------------------------------ Summary: Unable to add JGroups protocol at a given index via CLI Key: WFLY-6782 URL: https://issues.jboss.org/browse/WFLY-6782 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1624) Upgrade jboss-logmanager from version 2.0.3.Final to 2.0.4.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1624?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1624: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1638, https://github.com/wildfly/wildfly-core/pull/1639 (was: https://github.com/wildfly/wildfly-core/pull/1638) > Upgrade jboss-logmanager from version 2.0.3.Final to 2.0.4.Final > ---------------------------------------------------------------- > > Key: WFCORE-1624 > URL: https://issues.jboss.org/browse/WFCORE-1624 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > Upgrade {{org.jboss.logmanager:jboss-logmanager}} from version 2.0.3.Final to 2.0.4.Final. This will allow for module names with slots to be parsed correctly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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