June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-489) Add JavaDoc for the 'org.wildfly.security.mechanism' package and sub packages.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-489?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-489: --------------------------------- Fix Version/s: 1.1.0.Beta7 (was: 1.1.0.Beta6) > Add JavaDoc for the 'org.wildfly.security.mechanism' package and sub packages. > ------------------------------------------------------------------------------ > > Key: ELY-489 > URL: https://issues.jboss.org/browse/ELY-489 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-560) AuthenticationCompleteCallbackSasl*Factorys do not call the callback on early dispose()

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-560?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-560: --------------------------------- Fix Version/s: 1.1.0.Beta7 (was: 1.1.0.Beta6) > AuthenticationCompleteCallbackSasl*Factorys do not call the callback on early dispose() > --------------------------------------------------------------------------------------- > > Key: ELY-560 > URL: https://issues.jboss.org/browse/ELY-560 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > Fix For: 1.1.0.Beta7 > > > These classes did not take dispose() into account. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-559) Token-based authentication should forward authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-559?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-559: --------------------------------- Fix Version/s: 1.1.0.Beta7 (was: 1.1.0.Beta6) > Token-based authentication should forward authentication > -------------------------------------------------------- > > Key: ELY-559 > URL: https://issues.jboss.org/browse/ELY-559 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Mechanisms > Reporter: David Lloyd > Fix For: 1.1.0.Beta7 > > > Mechanisms that handle BearerTokenCredetials (ELY-557) should forward them as public or private credentials (ELY-473 / https://github.com/wildfly-security/wildfly-elytron/pull/434 ). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-558) Introduce generalized support for authentication timeout of mechanisms

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-558?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-558: --------------------------------- Fix Version/s: 1.1.0.Beta7 (was: 1.1.0.Beta6) > Introduce generalized support for authentication timeout of mechanisms > ---------------------------------------------------------------------- > > Key: ELY-558 > URL: https://issues.jboss.org/browse/ELY-558 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Mechanisms, Utils > Reporter: David Lloyd > Assignee: Farah Juma > Fix For: 1.1.0.Beta7 > > > Paraphrasing from HipChat discussion. > Generic mechanism wrappers for handling authentication timeout will not only support OTP-style credential read-modify-write authentication mechanisms, but generally avoid certain DoS conditions and failure states that would be associated with long locking of credentials (even in the read case). > This issue is to implement a wrapping mechanism factory (for at least SASL and possibly HTTP as well, eventually) which supports authentication timeout by judicious usage of concurrency primitives and timed executors. It is important to guarantee thread-safe access to the underlying mechanism, which are generally concurrency-unsafe. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-574) Release WildFly Elytron 1.1.0.Beta6

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-574?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-574. ---------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta6 > ----------------------------------- > > Key: ELY-574 > URL: https://issues.jboss.org/browse/ELY-574 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta6 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1596) Echo commands without arguments doesn't print existing variables - update help message

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1596?page=com.atlassian.jira.plugi... ] Alexey Loubyansky moved JBEAP-5046 to WFCORE-1596: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1596 (was: JBEAP-5046) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Target Release: (was: 7.backlog.GA) Affects Version/s: 3.0.0.Alpha1 (was: 7.0.1.CR1) > Echo commands without arguments doesn't print existing variables - update help message > -------------------------------------------------------------------------------------- > > Key: WFCORE-1596 > URL: https://issues.jboss.org/browse/WFCORE-1596 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > According to the help message: > {noformat} > If the command is executed w/o arguments then the command will print > all the existing variables with their values in the name=value format. > {noformat} > *actual* > {noformat} > [standalone@localhost:9990 /] set foo=bar > [standalone@localhost:9990 /] echo $foo > bar > [standalone@localhost:9990 /] echo > [standalone@localhost:9990 /] > {noformat} > *expected* > {noformat} > [standalone@localhost:9990 /] set foo=bar > [standalone@localhost:9990 /] echo $foo > bar > [standalone@localhost:9990 /] echo > foo=bar > [standalone@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6728) JDBC persistence-store for Artemis

by Bilge Ozpeynirci (JIRA)

[ https://issues.jboss.org/browse/WFLY-6728?page=com.atlassian.jira.plugin.... ] Bilge Ozpeynirci reassigned WFLY-6728: -------------------------------------- Assignee: Jeff Mesnil (was: Bilge Ozpeynirci) > JDBC persistence-store for Artemis > ---------------------------------- > > Key: WFLY-6728 > URL: https://issues.jboss.org/browse/WFLY-6728 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jochen Cordes > Assignee: Jeff Mesnil > > Apache ActiveMQ had the capability to store messages into a database via JDBC. In Apache ActiveMQ Artemis this has gone. > For a consistent backup data of various (co-located) systems participating in transactions should reside at the same datastore as otherwise this needs to be achieved through application software design (i.e. idempotent consumers etc.). > As in Apache ActiveMQ Artemis a JDBC Persistence-Store is about to be introduced we should also offer this capability on WildFly / EAP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6728) JDBC persistence-store for Artemis

by Jochen Cordes (JIRA)

Jochen Cordes created WFLY-6728: ----------------------------------- Summary: JDBC persistence-store for Artemis Key: WFLY-6728 URL: https://issues.jboss.org/browse/WFLY-6728 Project: WildFly Issue Type: Enhancement Components: JMS Affects Versions: 10.0.0.Final Reporter: Jochen Cordes Assignee: Bilge Ozpeynirci Apache ActiveMQ had the capability to store messages into a database via JDBC. In Apache ActiveMQ Artemis this has gone. For a consistent backup data of various (co-located) systems participating in transactions should reside at the same datastore as otherwise this needs to be achieved through application software design (i.e. idempotent consumers etc.). As in Apache ActiveMQ Artemis a JDBC Persistence-Store is about to be introduced we should also offer this capability on WildFly / EAP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6727) Transaction resource definition missing validator for default timeout

by Michal Petrov (JIRA)

Michal Petrov created WFLY-6727: ----------------------------------- Summary: Transaction resource definition missing validator for default timeout Key: WFLY-6727 URL: https://issues.jboss.org/browse/WFLY-6727 Project: WildFly Issue Type: Bug Components: Transactions Affects Versions: 10.0.0.Final Reporter: Michal Petrov Assignee: Michal Petrov Priority: Minor {{TransactionSubsystemRootResourceDefinition}} is missing a validator for {{default-timeout}}. This affects web console when something bigger than a 32-bit integer is entered. I see no specification but I'm assuming (0,MAX_INT) is the expected range. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2044) RequestCorrelator causes frequent boxing and autoboxing by using a Map<Long, Request>

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/JGRP-2044?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated JGRP-2044: ---------------------------------- Description: The JFR profiler is highlighting a significant amount of boxing and autoboxing, as the request is is treated as a {{long}} but this is used as an key for the {{Map<Long,Request>}}. We could try to either consistently use {{Long}} rather than {{long}}, or even better figure out an optimal data structure to replace the implementation of the Map to not require boxing of the keys. was: The JFR profiler is highlighting a significant amount of boxing and autoboxing, as the request is is treated as a {{long}} but this is used as an key for the {{Map<Long,Request>}}. We could try to either consistently use {{Long}} rather than {{long}, or even better figure out an optimal data structure to replace the implementation of the Map to not require boxing of the keys. > RequestCorrelator causes frequent boxing and autoboxing by using a Map<Long,Request> > ------------------------------------------------------------------------------------ > > Key: JGRP-2044 > URL: https://issues.jboss.org/browse/JGRP-2044 > Project: JGroups > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > The JFR profiler is highlighting a significant amount of boxing and autoboxing, as the request is is treated as a {{long}} but this is used as an key for the {{Map<Long,Request>}}. > We could try to either consistently use {{Long}} rather than {{long}}, or even better figure out an optimal data structure to replace the implementation of the Map to not require boxing of the keys. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 June 2016