September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELYWEB-21) Release Elytron Web 1.3.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELYWEB-21: -------------------------------------- Summary: Release Elytron Web 1.3.0.CR1 Key: ELYWEB-21 URL: https://issues.jboss.org/browse/ELYWEB-21 Project: Elytron Web Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.3.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4134) Upgrade Elytron Web to 1.3.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4134: ---------------------------------------- Summary: Upgrade Elytron Web to 1.3.0.CR1 Key: WFCORE-4134 URL: https://issues.jboss.org/browse/WFCORE-4134 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4133) Upgrade WildFly Elytron to 1.7.0.CR2

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4133: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.7.0.CR2 Key: WFCORE-4133 URL: https://issues.jboss.org/browse/WFCORE-4133 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-20) Upgrade to WildFly Elytron 1.7.0.CR2

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELYWEB-20: -------------------------------------- Summary: Upgrade to WildFly Elytron 1.7.0.CR2 Key: ELYWEB-20 URL: https://issues.jboss.org/browse/ELYWEB-20 Project: Elytron Web Issue Type: Component Upgrade Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.3.0.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1685) Incorrectly named attribute match-user in authentication-context in Elytron subsystem

by Jan Kalina (JIRA)

Jan Kalina created ELY-1685: ------------------------------- Summary: Incorrectly named attribute match-user in authentication-context in Elytron subsystem Key: ELY-1685 URL: https://issues.jboss.org/browse/ELY-1685 Project: WildFly Elytron Issue Type: Bug Components: XML Reporter: Jan Kalina Assignee: Jan Kalina Priority: Critical Fix For: 1.1.0.Beta49 Rule matcher {{match-user}} in authentication-context in Elytron subsystem internally uses {{org.wildfly.security.auth.client.MatchUserRule}}. This matcher works based on passed userinfo. However naming of {{match-user}} in Elytron subsystem indicates that just user part of userinfo should be used in matching. Also description in CLI is not correct, it says: _The user to match against._ It means one of following should be changed: * name of {{match-user}} * functionality of {{MatchUserRule}} Since Elytron client configuration file includes for the same matcher with name {{match-userinfo}} then I suggest to rename attribute {{match-user}} in {{authentication-context}} in Elytron subsystem to {{match-userinfo}} and improve description in CLI and XSD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11083) Incorrectly named attribute match-user in authentication-context in Elytron subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-11083?page=com.atlassian.jira.plugin... ] Jan Kalina moved ELY-1685 to WFLY-11083: ---------------------------------------- Project: WildFly (was: WildFly Elytron) Key: WFLY-11083 (was: ELY-1685) Component/s: Documentation (was: XML) Fix Version/s: (was: 1.1.0.Beta49) > Incorrectly named attribute match-user in authentication-context in Elytron subsystem > ------------------------------------------------------------------------------------- > > Key: WFLY-11083 > URL: https://issues.jboss.org/browse/WFLY-11083 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: user_experience > > Rule matcher {{match-user}} in authentication-context in Elytron subsystem internally uses {{org.wildfly.security.auth.client.MatchUserRule}}. This matcher works based on passed userinfo. However naming of {{match-user}} in Elytron subsystem indicates that just user part of userinfo should be used in matching. > Also description in CLI is not correct, it says: _The user to match against._ > It means one of following should be changed: > * name of {{match-user}} > * functionality of {{MatchUserRule}} > Since Elytron client configuration file includes for the same matcher with name {{match-userinfo}} then I suggest to rename attribute {{match-user}} in {{authentication-context}} in Elytron subsystem to {{match-userinfo}} and improve description in CLI and XSD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10208) [Artemis 2.x upgrade] Bad constant used in PropertySQLProviderFactory

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10208?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10208: --------------------------------- Fix Version/s: 14.0.0.Final > [Artemis 2.x upgrade] Bad constant used in PropertySQLProviderFactory > --------------------------------------------------------------------- > > Key: WFLY-10208 > URL: https://issues.jboss.org/browse/WFLY-10208 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: feature-branch-blocker > Fix For: 14.0.0.Final > > > There is bad constant used on line \[1\]. The SQL should release backup lock so BACKUP_LOCK_ROW_ID should be used instead of LIVE_LOCK_ROW_ID. > \[1\] https://github.com/jmesnil/wildfly/blob/be3af696141c9a6755583a5d1ab82f851... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10077) [Artemis 2.x upgrade] journal-node-manager-store-table attribute does not preserve its value

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10077?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10077: --------------------------------- Fix Version/s: 14.0.0.Final > [Artemis 2.x upgrade] journal-node-manager-store-table attribute does not preserve its value > --------------------------------------------------------------------------------------------- > > Key: WFLY-10077 > URL: https://issues.jboss.org/browse/WFLY-10077 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 14.0.0.Final > > > Writing to {{journal-node-manager-store-table}} attribute does not preserver its value and after restart default value is set again. > Output from CLI: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:read-attribute(name=journal-node-manager-store-table) > { > "outcome" => "success", > "result" => "NODE_MANAGER_STORE_NODE_1", > "response-headers" => {"process-state" => "reload-required"} > } > ...restart server here > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:read-attribute(name=journal-node-manager-store-table) > { > "outcome" => "success", > "result" => "NODE_MANAGER_STORE" > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1382) Destroy managed connection on failed reconnect

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1382?page=com.atlassian.jira.plugin... ] Brad Maxwell commented on JBJCA-1382: ------------------------------------- Resolved in 1.4.12, 1.3.9, 1.0.43 > Destroy managed connection on failed reconnect > ---------------------------------------------- > > Key: JBJCA-1382 > URL: https://issues.jboss.org/browse/JBJCA-1382 > Project: IronJacamar > Issue Type: Bug > Components: Core > Reporter: Brad Maxwell > Assignee: Stefano Maestri > > Destroy managed connection on failed reconnect -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1382) Destroy managed connection on failed reconnect

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1382?page=com.atlassian.jira.plugin... ] Brad Maxwell resolved JBJCA-1382. --------------------------------- Resolution: Done > Destroy managed connection on failed reconnect > ---------------------------------------------- > > Key: JBJCA-1382 > URL: https://issues.jboss.org/browse/JBJCA-1382 > Project: IronJacamar > Issue Type: Bug > Components: Core > Reporter: Brad Maxwell > Assignee: Stefano Maestri > > Destroy managed connection on failed reconnect -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 September 2018