jboss-jira August 2014

jboss-jira@lists.jboss.org

1 participants
1316 discussions

[JBoss JIRA] (WFLY-1877) Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-1877?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet updated WFLY-1877: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/6557 (was: https://github.com/wildfly/wildfly-core/pull/64, https://github.com/wildfly/wildfly/pull/6557) > Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute > ------------------------------------------------------------------------------------------ > > Key: WFLY-1877 > URL: https://issues.jboss.org/browse/WFLY-1877 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 9.0.0.CR1 > > > This attribute should support either a simple value or a complex one. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-39) Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute.

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFCORE-39: --------------------------------------- Summary: Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute. Key: WFCORE-39 URL: https://issues.jboss.org/browse/WFCORE-39 Project: WildFly Core Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Modules Affects Versions: 1.0.0.Alpha3 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-39) Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute.

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-39?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet updated WFCORE-39: ------------------------------------ Description: This attribute should support either a simple value or a complex one. > Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute. > -------------------------------------------------------------------------------------------- > > Key: WFCORE-39 > URL: https://issues.jboss.org/browse/WFCORE-39 > Project: WildFly Core > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Modules > Affects Versions: 1.0.0.Alpha3 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > This attribute should support either a simple value or a complex one. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3696) Security domain configuration doesn't allow empty or missing login-module-stack

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3696?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3696: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 901075|https://bugzilla.redhat.com/show_bug.cgi?id=901075] from ASSIGNED to POST > Security domain configuration doesn't allow empty or missing login-module-stack > ------------------------------------------------------------------------------- > > Key: WFLY-3696 > URL: https://issues.jboss.org/browse/WFLY-3696 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > > https://bugzilla.redhat.com/show_bug.cgi?id=901075 description: > project_key: JBPAPP6 > Adding a security domain with JASPI authentication fails if there is no (or is empty) login-module-stack. It should be possible to add custom ServerAuthModule, which doesn't use JAAS login modules. > {code:xml} > <security-domain name="jmx-console" cache-type="default"> > <authentication-jaspi> >  > <login-module-stack name="lm-stack"> > <login-module code="UsersRoles" flag="required"/> > </login-module-stack> > <auth-module code="org.jboss.example.CustomServerAuthModule" flag="required"> > <module-option name="option1" value="value1" /> > </auth-module> > </authentication-jaspi> > </security-domain> > {code} > It should be possible to remove here the login-module-stack element. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced deployments from the content repository

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-122: ---------------------------------------------- James Livingston <jlivings(a)redhat.com> changed the Status of [bug 1124689|https://bugzilla.redhat.com/show_bug.cgi?id=1124689] from NEW to CLOSED > Clean unreferenced deployments from the content repository > ---------------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced deployments from the content repository

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated WFLY-122: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1124689, https://bugzilla.redhat.com/show_bug.cgi?id=1018026 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1124689) > Clean unreferenced deployments from the content repository > ---------------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

← Newer
1
...
129
130
131
132
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2014