July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6853) Picketlink does not return SessionIndex in LogoutRequest

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6853?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6853: ----------------------------------------------- Fedor Gavrilov <fgavrilo(a)redhat.com> changed the Status of [bug 1353338|https://bugzilla.redhat.com/show_bug.cgi?id=1353338] from POST to MODIFIED > Picketlink does not return SessionIndex in LogoutRequest > -------------------------------------------------------- > > Key: WFLY-6853 > URL: https://issues.jboss.org/browse/WFLY-6853 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Vlado Pakan > Assignee: Vlado Pakan > > When logged out from application SAML logout message does not contain SessionIndex tag. > See referenced bugzilla for more information -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-603) AuthenticationConfiguration loosing mechanism ordering by using a HashSet instead of a LinkedHashSet

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-603?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-603: --------------------------------- If this is in reference to the authentication mechanisms - yes, it was meant as a filter, not a list of names. > AuthenticationConfiguration loosing mechanism ordering by using a HashSet instead of a LinkedHashSet > ---------------------------------------------------------------------------------------------------- > > Key: ELY-603 > URL: https://issues.jboss.org/browse/ELY-603 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-603) AuthenticationConfiguration loosing mechanism ordering by using a HashSet instead of a LinkedHashSet

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-603: ------------------------------------ Summary: AuthenticationConfiguration loosing mechanism ordering by using a HashSet instead of a LinkedHashSet Key: ELY-603 URL: https://issues.jboss.org/browse/ELY-603 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2062) TYPE_STRING does not handle unicode

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2062?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2062: --------------------------- Steps to Reproduce: {code:java} channel.send(new org.jgroups.Message(null, "\u1F601")); {code} Expected: Ironically, Jira fails on expected output. See http://apps.timwhitlock.info/emoji/tables/unicode Actual: garbage data was: {{ channel.send(new org.jgroups.Message(null, "\u1F601")); }} Expected: Ironically, Jira fails on expected output. See http://apps.timwhitlock.info/emoji/tables/unicode Actual: garbage data > TYPE_STRING does not handle unicode > ----------------------------------- > > Key: JGRP-2062 > URL: https://issues.jboss.org/browse/JGRP-2062 > Project: JGroups > Issue Type: Bug > Reporter: Cody Ebberson > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character. > For example, see objectToByteBuffer lines 561-567: > https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util.... > {code:java} > case TYPE_STRING: > String str=(String)obj; > int len=str.length(); > ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING); > for(int i=0; i < len; i++) > retval.put((byte)str.charAt(i)); > return retval.array(); > {code} > This code will incorrectly encode any String with non ASCII encoding. > There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2062) TYPE_STRING does not handle unicode

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2062?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2062: --------------------------- Description: In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character. For example, see objectToByteBuffer lines 561-567: https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util.... {code:java} case TYPE_STRING: String str=(String)obj; int len=str.length(); ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING); for(int i=0; i < len; i++) retval.put((byte)str.charAt(i)); return retval.array(); {code} This code will incorrectly encode any String with non ASCII encoding. There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path. was: In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character. For example, see objectToByteBuffer lines 561-567: https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util.... {{case TYPE_STRING: String str=(String)obj; int len=str.length(); ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING); for(int i=0; i < len; i++) retval.put((byte)str.charAt(i)); return retval.array();}} This code will incorrectly encode any String with non ASCII encoding. There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path. > TYPE_STRING does not handle unicode > ----------------------------------- > > Key: JGRP-2062 > URL: https://issues.jboss.org/browse/JGRP-2062 > Project: JGroups > Issue Type: Bug > Reporter: Cody Ebberson > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character. > For example, see objectToByteBuffer lines 561-567: > https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util.... > {code:java} > case TYPE_STRING: > String str=(String)obj; > int len=str.length(); > ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING); > for(int i=0; i < len; i++) > retval.put((byte)str.charAt(i)); > return retval.array(); > {code} > This code will incorrectly encode any String with non ASCII encoding. > There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-602) Add support for SASL mechanism ordering by name.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-602?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-602: --------------------------------- Description: We previously relied on ordering of the factories although this does not work well once multiple modules are in use, add SortedMechanismSasl*Factory implementations that can take a Comparator to sort the names from a delegate. (was: Ideally we would actually have policy to sort mechanisms however for the moment we can at the very least get our factories into a desired order.) > Add support for SASL mechanism ordering by name. > ------------------------------------------------ > > Key: ELY-602 > URL: https://issues.jboss.org/browse/ELY-602 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta7 > > > We previously relied on ordering of the factories although this does not work well once multiple modules are in use, add SortedMechanismSasl*Factory implementations that can take a Comparator to sort the names from a delegate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-602) Re-instate SASL mechanism factory ordering.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-602?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-602: --------------------------------- Issue Type: Feature Request (was: Task) > Re-instate SASL mechanism factory ordering. > ------------------------------------------- > > Key: ELY-602 > URL: https://issues.jboss.org/browse/ELY-602 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta7 > > > Ideally we would actually have policy to sort mechanisms however for the moment we can at the very least get our factories into a desired order. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-602) Add support for SASL mechanism ordering by name.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-602?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-602: --------------------------------- Summary: Add support for SASL mechanism ordering by name. (was: Re-instate SASL mechanism factory ordering.) > Add support for SASL mechanism ordering by name. > ------------------------------------------------ > > Key: ELY-602 > URL: https://issues.jboss.org/browse/ELY-602 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta7 > > > Ideally we would actually have policy to sort mechanisms however for the moment we can at the very least get our factories into a desired order. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1673) Testsuite: tests for CLI controller aliases

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1673?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1673: ------------------------------------------ I put the CLI component on this so the CLI devs (i.e. [~jfdenise]) are aware that this work is being done. > Testsuite: tests for CLI controller aliases > ------------------------------------------- > > Key: WFCORE-1673 > URL: https://issues.jboss.org/browse/WFCORE-1673 > Project: WildFly Core > Issue Type: Task > Components: CLI, Test Suite > Reporter: Martin Schvarcbacher > Assignee: Martin Schvarcbacher > Priority: Minor > > Added integration tests for server aliases defined in jboss-cli.xml > Usage in bin/jboss-cli.xml: > {code:xml} > <controllers> > <controller name="ServerOne"> > <protocol>http-remoting</protocol> > <host>localhost</host> > <port>9990</port> > </controller> > </controllers> > {code} > {code:bash} > ./bin/jboss-cli.sh --controller=ServerOne --connect > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1673) Testsuite: tests for CLI controller aliases

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1673?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1673: ------------------------------------- Component/s: CLI > Testsuite: tests for CLI controller aliases > ------------------------------------------- > > Key: WFCORE-1673 > URL: https://issues.jboss.org/browse/WFCORE-1673 > Project: WildFly Core > Issue Type: Task > Components: CLI, Test Suite > Reporter: Martin Schvarcbacher > Assignee: Martin Schvarcbacher > Priority: Minor > > Added integration tests for server aliases defined in jboss-cli.xml > Usage in bin/jboss-cli.xml: > {code:xml} > <controllers> > <controller name="ServerOne"> > <protocol>http-remoting</protocol> > <host>localhost</host> > <port>9990</port> > </controller> > </controllers> > {code} > {code:bash} > ./bin/jboss-cli.sh --controller=ServerOne --connect > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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