March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3077) Convert command line IPv6 URL literals to address literals

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3077?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3077: ----------------------------------- Bugzilla Update: (was: Perform) > Convert command line IPv6 URL literals to address literals > ---------------------------------------------------------- > > Key: WFLY-3077 > URL: https://issues.jboss.org/browse/WFLY-3077 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 8.0.1.Final > > > When people provide URL-style values like [::1] for command line args like -b, convert them to address values (i.e. strip the enclosing brackets.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3077) Convert command line IPv6 URL literals to address literals

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3077: -------------------------------------- Summary: Convert command line IPv6 URL literals to address literals Key: WFLY-3077 URL: https://issues.jboss.org/browse/WFLY-3077 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 8.0.1.Final When people provide URL-style values like [::1] for command line args like -b, convert them to address values (i.e. strip the enclosing brackets.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3076) ModelControllerMBeanHelper constructor invokes unnecessary management op

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3076?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-3076: ---------------------------------------- This, BTW is the cause of the test failure at http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=11936. The read-attribute call is ending up in the log and the test doesn't expect that. > ModelControllerMBeanHelper constructor invokes unnecessary management op > ------------------------------------------------------------------------ > > Key: WFLY-3076 > URL: https://issues.jboss.org/browse/WFLY-3076 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, JMX > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.1.Final > > > ModelControllerMBeanHelper is invoking a read-attribute management op in its constructor to find out of the process is a standalone server. This is not necessary -- JmxSubsystemAdd can find this out from the OperationContext and pass this information through to the ModelControllerMBeanHelper it indirectly creates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3076) ModelControllerMBeanHelper constructor invokes unnecessary management op

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3076: -------------------------------------- Summary: ModelControllerMBeanHelper constructor invokes unnecessary management op Key: WFLY-3076 URL: https://issues.jboss.org/browse/WFLY-3076 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management, JMX Affects Versions: 8.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.1.Final ModelControllerMBeanHelper is invoking a read-attribute management op in its constructor to find out of the process is a standalone server. This is not necessary -- JmxSubsystemAdd can find this out from the OperationContext and pass this information through to the ModelControllerMBeanHelper it indirectly creates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3071) upgrade Generic JMS RA to 1.0.2.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3071?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3071: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1073354|https://bugzilla.redhat.com/show_bug.cgi?id=1073354] from POST to MODIFIED > upgrade Generic JMS RA to 1.0.2.Final > ------------------------------------- > > Key: WFLY-3071 > URL: https://issues.jboss.org/browse/WFLY-3071 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3073) MBeanServer.createMBean methods that take a classloader don't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3073?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3073: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1073106|https://bugzilla.redhat.com/show_bug.cgi?id=1073106] from NEW to MODIFIED > MBeanServer.createMBean methods that take a classloader don't work > ------------------------------------------------------------------ > > Key: WFLY-3073 > URL: https://issues.jboss.org/browse/WFLY-3073 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: 8.0.0.Final > Reporter: Stuart Douglas > Assignee: Kabir Khan > Fix For: 8.0.1.Final > > > The MBeanServer.createMBean methods that take an "ObjectName loaderName" argument are completely broken in EAP 6. > These methods call findDelegate to make sure there is already an existing MBean registered with the given name passed in for the new MBean, or else it throws an exception. > This is obviously wrong, as there'd be no point in calling createMBean if it already existed. > javax.management.InstanceNotFoundException: test:service=Test > at org.jboss.as.jmx.PluggableMBeanServerImpl.findDelegate(PluggableMBeanServerImpl.java:1083) > at org.jboss.as.jmx.PluggableMBeanServerImpl.createMBean(PluggableMBeanServerImpl.java:253) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-803) SecureIdentityLoginModule (and ConfiguredIdentityLoginModule) results are not cached by the JAAS cache

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-803?page=com.atlassian.jira.plug... ] Derek Horton commented on SECURITY-803: --------------------------------------- Patch has been committed to trunk: https://svn.jboss.org/repos/picketbox/trunk > SecureIdentityLoginModule (and ConfiguredIdentityLoginModule) results are not cached by the JAAS cache > ------------------------------------------------------------------------------------------------------ > > Key: SECURITY-803 > URL: https://issues.jboss.org/browse/SECURITY-803 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-803.patch > > > In EAP 6, when using the SecureIdentityLoginModule to encrypt datasource passwords, the results are not cached by the JAAS cache. In EAP 5, the results are cached. This can lead to a performance issue. > The root cause appears to be that the EAP 6 JAAS cache does not allow for a JAAS cache key to be null. > The issue only occurs when the application that uses the datasource is not secured. In this situation, the principal is null when isValid() and updateCache() are called. When the application is secured, the results are cached. I think it is working because the result of the SecureIdentityLoginModule are cached using the authenticated user's principal as the cache key. > Workaround: > Use vault for encrypting the database password. This does not use a JAAS login module so the JAAS cache and login module are completely avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-803) SecureIdentityLoginModule (and ConfiguredIdentityLoginModule) results are not cached by the JAAS cache

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-803?page=com.atlassian.jira.plug... ] Derek Horton resolved SECURITY-803. ----------------------------------- Resolution: Done > SecureIdentityLoginModule (and ConfiguredIdentityLoginModule) results are not cached by the JAAS cache > ------------------------------------------------------------------------------------------------------ > > Key: SECURITY-803 > URL: https://issues.jboss.org/browse/SECURITY-803 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-803.patch > > > In EAP 6, when using the SecureIdentityLoginModule to encrypt datasource passwords, the results are not cached by the JAAS cache. In EAP 5, the results are cached. This can lead to a performance issue. > The root cause appears to be that the EAP 6 JAAS cache does not allow for a JAAS cache key to be null. > The issue only occurs when the application that uses the datasource is not secured. In this situation, the principal is null when isValid() and updateCache() are called. When the application is secured, the results are cached. I think it is working because the result of the SecureIdentityLoginModule are cached using the authenticated user's principal as the cache key. > Workaround: > Use vault for encrypting the database password. This does not use a JAAS login module so the JAAS cache and login module are completely avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-803) SecureIdentityLoginModule (and ConfiguredIdentityLoginModule) results are not cached by the JAAS cache

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-803?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-803: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1069885, https://bugzilla.redhat.com/show_bug.cgi?id=1069886, https://bugzilla.redhat.com/show_bug.cgi?id=1073646 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1069885, https://bugzilla.redhat.com/show_bug.cgi?id=1069886) > SecureIdentityLoginModule (and ConfiguredIdentityLoginModule) results are not cached by the JAAS cache > ------------------------------------------------------------------------------------------------------ > > Key: SECURITY-803 > URL: https://issues.jboss.org/browse/SECURITY-803 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-803.patch > > > In EAP 6, when using the SecureIdentityLoginModule to encrypt datasource passwords, the results are not cached by the JAAS cache. In EAP 5, the results are cached. This can lead to a performance issue. > The root cause appears to be that the EAP 6 JAAS cache does not allow for a JAAS cache key to be null. > The issue only occurs when the application that uses the datasource is not secured. In this situation, the principal is null when isValid() and updateCache() are called. When the application is secured, the results are cached. I think it is working because the result of the SecureIdentityLoginModule are cached using the authenticated user's principal as the cache key. > Workaround: > Use vault for encrypting the database password. This does not use a JAAS login module so the JAAS cache and login module are completely avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2936) "Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction" error in migrated seam 2.2.2 application

by Vijay Kumar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2936?page=com.atlassian.jira.plugin.... ] Vijay Kumar commented on WFLY-2936: ----------------------------------- Hi Eduardo, fix (build 991) is good. I don't see this error anymore. Thanks a lot for quick fix. Vijay > "Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction" error in migrated seam 2.2.2 application > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2936 > URL: https://issues.jboss.org/browse/WFLY-2936 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Environment: Windows 7 64bit > Java 1.7.0_51 > WildFly 8.0.0.Final > JBoss Seam 2.2.2.Final > Reporter: Dimitris Keramidas > Assignee: Eduardo Martins > Fix For: 8.0.1.Final > > Attachments: Auth.java, Authenticator.java, components.xml, jboss-deployment-structure.xml, server.log > > > The error is fired when attempting to call a transaction-enabled EJB method, from a seam component. Specifically the authentication component. > In order to get to this position, the project's deployment descriptors had to be migrated. Furthermore, mojarra version 1.2_15 was deployed to WildFly, as described by this link: https://community.jboss.org/wiki/DesignOfWildFlyMulti-JSFFeature > Please see attached logs and descriptors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 March 2014