November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-822) Remove the 'NET' project from JBoss Negotiation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-822?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-822: -------------------------------------- Fix Version/s: Negotiation_2_3_6_Final (was: Negotiation_2_3_5.Final) > Remove the 'NET' project from JBoss Negotiation > ----------------------------------------------- > > Key: SECURITY-822 > URL: https://issues.jboss.org/browse/SECURITY-822 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_11, Negotiation_2_3_6_Final > > > The net project is not used in AS 7, EAP 6 or WildFly so time to delete it. > In WildFly 9 an alternative SASL based approach will be used for EJB invocations. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-870) Release JBoss Negotiation 2.3.5.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-870?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-870. --------------------------------------- Resolution: Done > Release JBoss Negotiation 2.3.5.Final > ------------------------------------- > > Key: SECURITY-870 > URL: https://issues.jboss.org/browse/SECURITY-870 > Project: PicketBox > Issue Type: Release > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_5.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4114) Upgrade to JBoss Negotiation 2.3.5.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-4114: -------------------------------------- Summary: Upgrade to JBoss Negotiation 2.3.5.Final Key: WFLY-4114 URL: https://issues.jboss.org/browse/WFLY-4114 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-869) Session created if it doesn't exist even if authentication does not occur.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-869?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-869. --------------------------------------- Resolution: Done > Session created if it doesn't exist even if authentication does not occur. > -------------------------------------------------------------------------- > > Key: SECURITY-869 > URL: https://issues.jboss.org/browse/SECURITY-869 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_5.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-275) Migrate soem RBAC test from WildFly full to WFCORE

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFCORE-275: ---------------------------------------- Summary: Migrate soem RBAC test from WildFly full to WFCORE Key: WFCORE-275 URL: https://issues.jboss.org/browse/WFCORE-275 Project: WildFly Core Issue Type: Task Components: Test Suite Affects Versions: 1.0.0.Alpha13 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet All RBAC integration testing is currently done in the WILDFLY project whereas the code is in WFCORE. Migrate some tests which are not related to the RBAC usage in WILDFLY to WFCORE. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-274) The CLI command "read-boot-errors" does not include the timestamp of the error event

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-274?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-274: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1160898 > The CLI command "read-boot-errors" does not include the timestamp of the error event > ------------------------------------------------------------------------------------ > > Key: WFCORE-274 > URL: https://issues.jboss.org/browse/WFCORE-274 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > The CLI command "read-boot-errors" does not include the timestamp of the error event. For anyone using this command for diagnostic purposes, the absence of an event's timestamp decreases the usefulness of the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-274) The CLI command "read-boot-errors" does not include the timestamp of the error event

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-274?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-274: ------------------------------------------------ Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 1160898|https://bugzilla.redhat.com/show_bug.cgi?id=1160898] from NEW to ASSIGNED > The CLI command "read-boot-errors" does not include the timestamp of the error event > ------------------------------------------------------------------------------------ > > Key: WFCORE-274 > URL: https://issues.jboss.org/browse/WFCORE-274 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > The CLI command "read-boot-errors" does not include the timestamp of the error event. For anyone using this command for diagnostic purposes, the absence of an event's timestamp decreases the usefulness of the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-274) The CLI command "read-boot-errors" does not include the timestamp of the error event

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFCORE-274: ---------------------------------------- Summary: The CLI command "read-boot-errors" does not include the timestamp of the error event Key: WFCORE-274 URL: https://issues.jboss.org/browse/WFCORE-274 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 1.0.0.Alpha13 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet The CLI command "read-boot-errors" does not include the timestamp of the error event. For anyone using this command for diagnostic purposes, the absence of an event's timestamp decreases the usefulness of the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1650) Legacy subsystem testing needs some classloading exclusion mecanism

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1650?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1650: ----------------------------------------------- Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from ASSIGNED to POST > Legacy subsystem testing needs some classloading exclusion mecanism > ------------------------------------------------------------------- > > Key: WFLY-1650 > URL: https://issues.jboss.org/browse/WFLY-1650 > Project: WildFly > Issue Type: Bug > Components: Logging, Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Fix For: 8.0.0.Beta1 > > > When translation messages are used (which is the case of EAP) we have conflicts between generated $logger classes when testing submodules. > Some $logger classes exis thus they are loaded by the parent classloader before the childfirstclassloader tries to load them, thus we have a potential ClassCastException brewing. > For exemple this breaks the EAP build on a French OS. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-134) Make sure CLIWrapper doesn't use default encoding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-134: ------------------------------------------------ Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from ASSIGNED to POST > Make sure CLIWrapper doesn't use default encoding > ------------------------------------------------- > > Key: WFCORE-134 > URL: https://issues.jboss.org/browse/WFCORE-134 > Project: WildFly Core > Issue Type: Bug > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 1.0.0.Alpha9 > > > CLIWrapper is using the default encoding which might lead to issue with non US locales. > Also take advantage of this fix to remove some hard coded strings from tests. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 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 November 2014