July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name

by Robert Cernak (JIRA)

[ https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin.... ] Robert Cernak closed JGRP-2227. ------------------------------- > Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name > ----------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2227 > URL: https://issues.jboss.org/browse/JGRP-2227 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.6 > Reporter: Robert Cernak > Assignee: Bela Ban > Fix For: 4.0.13 > > Attachments: jgroupsDoesNotThrowSecurityExceptionWithJgroups4012.zip, jgroupsLogs.zip, traceLogs.zip > > > I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false; > In this way authentication should be false and I should get SecurityException. > When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name. > I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10667) Upgrade WildFly Core 6.0.0.Alpha3

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-10667: ---------------------------------- Summary: Upgrade WildFly Core 6.0.0.Alpha3 Key: WFLY-10667 URL: https://issues.jboss.org/browse/WFLY-10667 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3877) Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components.

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3877?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3877: -------------------------------- Fix Version/s: 6.0.0.Alpha4 (was: 6.0.0.Alpha3) > Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components. > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3877 > URL: https://issues.jboss.org/browse/WFCORE-3877 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Martin Mazanek > Fix For: 6.0.0.Alpha4 > > > Presently custom components within the Elytron subsystem are required to implement the 'org.wildfly.extension.elytron.Configurable' interface if they wish to support receiving a Map of configuration Strings. > This means that the custom component needs to depend on both the WildFly Elytron project and the subsystem. > It should be possible for components to add the following method without implementing the interface and be configurable. > {noformat} > void initialize(final Map<String, String> configuration); > {noformat} > We also have a long standing issue in that if we add a new component to WildFly Elytron it can not be used until we can add a resource to configure it. By supporting configurable custom components without needing a dependency on the subsystem new components added to WildFly Elytron could be usable whilst the subsystem definitions catch up. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3952) Unable to run -DallTests -Delytron builds

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3952?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3952: -------------------------------- Fix Version/s: 6.0.0.Alpha4 (was: 6.0.0.Alpha3) > Unable to run -DallTests -Delytron builds > ----------------------------------------- > > Key: WFCORE-3952 > URL: https://issues.jboss.org/browse/WFCORE-3952 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 6.0.0.Alpha4 > > > Attempting to use -DallTests -Delytron results in the following error: - > {noformat} > [ERROR] } > [ERROR] Cannot start embedded Host Controller: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYHC0097: Domain base directory does not exist: /home/darranl/src/wildfly13/wildfly-core/testsuite/standalone/target/wildfly-core/domain > {noformat} > I believe this is actually caused by WFCORE-3769 which provisions a standalone server only. > We don't currently run -Delytron jobs for WildFly Core but this bug causes problems with experimental builds where we may want to use -Delytron. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3945) Support associating a SecurityDomain with a web deployment instead of a http-authentication-factory

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3945?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3945: -------------------------------- Fix Version/s: 6.0.0.Alpha4 (was: 6.0.0.Alpha3) > Support associating a SecurityDomain with a web deployment instead of a http-authentication-factory > --------------------------------------------------------------------------------------------------- > > Key: WFCORE-3945 > URL: https://issues.jboss.org/browse/WFCORE-3945 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 6.0.0.Alpha4 > > > The default configuration related to the http-authentication-factory comes from the Elytron subsystem in WildFly Core so this issue is to just handle the default configuration side of the change. > The default resource was only used for the mechanisms defined in the servlet specification anyway so can be removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-41) Implement HOME and END keys

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-41?page=com.atlassian.jira.plugin.s... ] Erich Duda closed WFWIP-41. --------------------------- Resolution: Done > Implement HOME and END keys > --------------------------- > > Key: WFWIP-41 > URL: https://issues.jboss.org/browse/WFWIP-41 > Project: WildFly WIP > Issue Type: Task > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > This is related to WFCORE-3568. Based on [proposal|https://github.com/wildfly/wildfly-proposals/pull/48/files] the scrolling feature should support also HOME and END keys. However they are not implemented yet so I've created this Jira as reminder. > In the analysis the keys don't have any one char alternatives which help at testing. Please introduce them as well. Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8066) Switch to TCP_NIO2 as the new default transport protocol

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8066?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8066: --------------------------------- Summary: Switch to TCP_NIO2 as the new default transport protocol (was: Investigate TCP_NIO2 as the new transport protocol default) > Switch to TCP_NIO2 as the new default transport protocol > -------------------------------------------------------- > > Key: WFLY-8066 > URL: https://issues.jboss.org/browse/WFLY-8066 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8066) Switch to TCP_NIO2 as the new default transport protocol

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8066?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-8066: ------------------------------------ Assignee: Paul Ferraro (was: Radoslav Husar) > Switch to TCP_NIO2 as the new default transport protocol > -------------------------------------------------------- > > Key: WFLY-8066 > URL: https://issues.jboss.org/browse/WFLY-8066 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3953) JBoss CLI doesn't work on OpenShift

by Martin Styk (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3953?page=com.atlassian.jira.plugi... ] Martin Styk commented on WFCORE-3953: ------------------------------------- [~jdenise], here is output of first two points. {code} sh-4.2$ stty -a speed 38400 baud; rows 55; columns 211; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel -iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke {code} {code} sh-4.2$ tty not a tty {code} > JBoss CLI doesn't work on OpenShift > ----------------------------------- > > Key: WFCORE-3953 > URL: https://issues.jboss.org/browse/WFCORE-3953 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: OpenShift/MiniShift > * minishift v1.15.1+f19ac09 > * CDK v3.4.0-2 > EAP CD12 > * Registry registry.access.redhat.com > * Namespace/Repository jboss-eap-7-tech-preview/eap-cd-openshift > * Tag 12.0-14 > Reporter: Martin Styk > Assignee: Jean-Francois Denise > Priority: Critical > > I am unable to access JBoss CLI console running EAP CD12 on OpenShift. > On OS webconsole terminal: > {code} > cd $JBOSS_HOME/bin > sh jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > {code} > No new line appears and I am not able to enter any character, thus I can not connect. I can only exit JBoss CLI console with Ctrl + C. > With CD12 it doesn't work neither with terminal session on web console, nor with {{oc rsh <pod>}} from local terminal. > This doesn't happen with EAP 7.0 and EAP 7.1 openshift images. EAP CD12 distribution (not the OpenShift image) is also not affected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3953) JBoss CLI doesn't work on OpenShift

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3953?page=com.atlassian.jira.plugi... ] Jean-Francois Denise closed WFCORE-3953. ---------------------------------------- Resolution: Duplicate Issue That is a duplicate of WFCORE-3667, already fixed in aesh-readline 1,6, wildfly core 5.0.0.Alpha2. > JBoss CLI doesn't work on OpenShift > ----------------------------------- > > Key: WFCORE-3953 > URL: https://issues.jboss.org/browse/WFCORE-3953 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: OpenShift/MiniShift > * minishift v1.15.1+f19ac09 > * CDK v3.4.0-2 > EAP CD12 > * Registry registry.access.redhat.com > * Namespace/Repository jboss-eap-7-tech-preview/eap-cd-openshift > * Tag 12.0-14 > Reporter: Martin Styk > Assignee: Jean-Francois Denise > Priority: Critical > > I am unable to access JBoss CLI console running EAP CD12 on OpenShift. > On OS webconsole terminal: > {code} > cd $JBOSS_HOME/bin > sh jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > {code} > No new line appears and I am not able to enter any character, thus I can not connect. I can only exit JBoss CLI console with Ctrl + C. > With CD12 it doesn't work neither with terminal session on web console, nor with {{oc rsh <pod>}} from local terminal. > This doesn't happen with EAP 7.0 and EAP 7.1 openshift images. EAP CD12 distribution (not the OpenShift image) is also not affected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 July 2018