February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5550) Formalize web session clustering modules into a proper subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5550?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5550: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Formalize web session clustering modules into a proper subsystem > ---------------------------------------------------------------- > > Key: WFLY-5550 > URL: https://issues.jboss.org/browse/WFLY-5550 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.0.0.CR3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose. > Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation. > The subsystem would define the requisite cache-container, exposed as a capability. > This subsystem would exposes a number of profiles, containing the configuration traditionally specified in jboss-web.xml, as well as the cache configuration to use (specified by cache-container + cache name). jboss-web.xml would only need to reference a profile by name, or, if unspecified, use the default profile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5497) Add <distributable/> to shared-session-config schema

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5497?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5497: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Add <distributable/> to shared-session-config schema > ---------------------------------------------------- > > Key: WFLY-5497 > URL: https://issues.jboss.org/browse/WFLY-5497 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Web (Undertow) > Affects Versions: 10.0.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > Currently, the shared-session-config does not indicate whether a distributable or non-distributable session manager should be used. Consequently, we assign the session manager implementation based on the availability of the module providing the distributed implementation. Since the default infinispan web session configuration attempts to passivate sessions on shutdown, users will see NotSerializableExceptions on shutdown if they use non-serializable session attributes - even if their web applications do not define themselves as being <distributable/>. > To clarify this ambiguity, we should add a <distributable/> element (a la web.xml) to the shared-session-config schema to determine which session manager implementation to use. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5427) If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5427?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5427: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore > ---------------------------------------------------------------------------------------- > > Key: WFLY-5427 > URL: https://issues.jboss.org/browse/WFLY-5427 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.CR2 > Reporter: Ondra Chaloupka > Assignee: Amos Feng > Priority: Minor > Fix For: 12.0.0.Final > > > Directory of transaction object store is named {{standalone/data/tx-object-store/HornetqObjectStore}}. The WFLY 10 does not use HornetQ object store but it uses ActiveMQ Artemis object store. That's same for the Transaction subsystem. > The journal dirctory should be renamed to {{JournalObjectStore}} or something similar. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5406) Update to add a testcase for the journal store setting in the transaction subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5406?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5406: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Update to add a testcase for the journal store setting in the transaction subsystem > ----------------------------------------------------------------------------------- > > Key: WFLY-5406 > URL: https://issues.jboss.org/browse/WFLY-5406 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, Transactions > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 12.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5265) Use WildFly Common for null param checks

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5265?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5265: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Use WildFly Common for null param checks > ---------------------------------------- > > Key: WFLY-5265 > URL: https://issues.jboss.org/browse/WFLY-5265 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > Fix For: 12.0.0.Final > > > For each module, do the following: > * Locate any/all null param check methods in the log msg > * Replace them with calls to org.wildfly.common.Assert#checkNotNullParam or related method as needed > * Replace the old null param check method with a comment that reserves the ID and shows that it was previously used for that purpose -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5141) Custom operation for setting of process-id-*

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5141?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5141: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Custom operation for setting of process-id-* > -------------------------------------------- > > Key: WFLY-5141 > URL: https://issues.jboss.org/browse/WFLY-5141 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Beta1 > Reporter: Ondra Chaloupka > Assignee: Amos Feng > Priority: Minor > Labels: ux > Fix For: 12.0.0.Final > > > When you want to set generation of process-id-* - either as uuid or as socket id the way to set it and set it back is inconsistent. In one direction you need to use composite operation in other direction you can't use it. > All this is discussed in jiras WFLY-2623 and WFLY-5126 > As result of discussion https://issues.jboss.org/browse/WFLY-2623#comment-13100037 this issue is raised. > It would be much better for user to have single way how to do this switching and custom operation could solve this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6365) Update permissions to use Elytron permission helper API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6365?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6365: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Update permissions to use Elytron permission helper API > ------------------------------------------------------- > > Key: WFLY-6365 > URL: https://issues.jboss.org/browse/WFLY-6365 > Project: WildFly > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 12.0.0.Final > > > The Elytron permission base classes ensure spec compliance including serialization guarantees while also drastically reducing the amount of code required to implement permission classes correctly and improving performance and memory overhead, especially when a security manager is engaged. Use these classes as base classes for all WildFly permission classes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6085) Wrong AdvancedADLdap mapping in ModulesMap

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6085?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6085: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Wrong AdvancedADLdap mapping in ModulesMap > ------------------------------------------ > > Key: WFLY-6085 > URL: https://issues.jboss.org/browse/WFLY-6085 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Fix For: 12.0.0.Final > > > There is wrong AdvancedADLdap mapping in ModulesMap. > In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap". > https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/mai... > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > We suggest some like this for backward compatibility: > Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping. > {code} > put("AdvancedAdLdap", AdvancedADLoginModule.class.getName()); > put("AdvancedADLdap", AdvancedADLoginModule.class.getName()); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5847) Upgrade jberet-core to 1.3.0.Alpha1

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5847?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5847: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Upgrade jberet-core to 1.3.0.Alpha1 > ----------------------------------- > > Key: WFLY-5847 > URL: https://issues.jboss.org/browse/WFLY-5847 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Affects Versions: 11.0.0.Alpha1 > Reporter: Cheng Fang > Assignee: James Perkins > Fix For: 12.0.0.Final > > > JBeret 1.3.0.Alpha1 was released on 12/14/2015, and ready to be integrated into WildFly 11: > https://issues.jboss.org/projects/JBERET/versions/12327883 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5776) Make use of the principals to roles map as defined within web deployments.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5776?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5776: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Make use of the principals to roles map as defined within web deployments. > -------------------------------------------------------------------------- > > Key: WFLY-5776 > URL: https://issues.jboss.org/browse/WFLY-5776 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 12.0.0.Final > > > Will follow up on this one after the authentication is handled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018