May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-735) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-735?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-735: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 953513|https://bugzilla.redhat.com/show_bug.cgi?id=953513] from ON_QA to VERIFIED > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-735 > URL: https://issues.jboss.org/browse/SECURITY-735 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-737) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-737?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-737: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 953513|https://bugzilla.redhat.com/show_bug.cgi?id=953513] from ON_QA to VERIFIED > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-737 > URL: https://issues.jboss.org/browse/SECURITY-737 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_3 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > cloned from: https://bugzilla.redhat.com/show_bug.cgi?id=953513 > back port for EAP 5.x upstream -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-737) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-737?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-737: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> made a comment on [bug 953513|https://bugzilla.redhat.com/show_bug.cgi?id=953513] Verified in EAP 6.1.0.ER6. PRs with regression tests: https://github.com/wildfly/wildfly/pull/4456 https://github.com/jbossas/jboss-eap/pull/130 > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-737 > URL: https://issues.jboss.org/browse/SECURITY-737 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_1_3 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > cloned from: https://bugzilla.redhat.com/show_bug.cgi?id=953513 > back port for EAP 5.x upstream -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-735) spnego AdvancedLdapLoginModule cannot cope with roles contains a slash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-735?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-735: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> made a comment on [bug 953513|https://bugzilla.redhat.com/show_bug.cgi?id=953513] Verified in EAP 6.1.0.ER6. PRs with regression tests: https://github.com/wildfly/wildfly/pull/4456 https://github.com/jbossas/jboss-eap/pull/130 > spnego AdvancedLdapLoginModule cannot cope with roles contains a slash > ---------------------------------------------------------------------- > > Key: SECURITY-735 > URL: https://issues.jboss.org/browse/SECURITY-735 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-179) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-179?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-179: ---------------------------------------------- Aleksandar Kostadinov <akostadi(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] Michal, that's right, I meant 6.1.0 ER5 > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: WFLY-179 > URL: https://issues.jboss.org/browse/WFLY-179 > Project: WildFly > Issue Type: Bug > Components: CLI, Clustering > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-82) Wrong injection made by container

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-82?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-82: --------------------------------------------- Zbyněk Roubalík <zroubali(a)redhat.com> made a comment on [bug 909914|https://bugzilla.redhat.com/show_bug.cgi?id=909914] Verified on EAP 6.1.0.ER6 > Wrong injection made by container > --------------------------------- > > Key: WFLY-82 > URL: https://issues.jboss.org/browse/WFLY-82 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, JPA / Hibernate > Reporter: Luan Cestari > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Description of problem: > I got an issue in a salesforce case [1] about an incorrect injection. > [1] https://c.na7.visual.force.com/apex/Case_View?id=500A000000CRqDG&sfdc.ove... > Version-Release number of selected component (if applicable): > How reproducible: > To reproduce the case is required to have two PersistentUnit (PU), a Abstract class with a setter method to inject one PU and others classes inheriting the Abstract class and overriding the setter method to inject a different PU. In the runtime, the container inject twice the PU, first the correct PU and then the PU described in super class. > I talked with the client (who is a Red Hat consultant) and we made the attached project based on a very simple JBoss example to reproduce the issue which happens in EAP6. I put a lot of 'println' to be very clear (even printing stacktrace to show who is calling). The most important files are: > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/BaseDAO.java -- The abstract class with the default PU injection > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/SecondaryMemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberListProducer.java -- The class which inject the MemberListProducer and SecondaryMemberRepository > -> hibernate4Test/src/main/resources/META-INF/persistence.xml -- We changed the configuration here to each PU have a different entity mapped > Steps to Reproduce: > > Actual results: > The EM injection occurs twice, which the last one the wrong EM. > Expected results: > Just one injection occurs. > Additional info: -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-82) Wrong injection made by container

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-82?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-82: --------------------------------------------- Zbyněk Roubalík <zroubali(a)redhat.com> changed the Status of [bug 909914|https://bugzilla.redhat.com/show_bug.cgi?id=909914] from ON_QA to VERIFIED > Wrong injection made by container > --------------------------------- > > Key: WFLY-82 > URL: https://issues.jboss.org/browse/WFLY-82 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, JPA / Hibernate > Reporter: Luan Cestari > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Description of problem: > I got an issue in a salesforce case [1] about an incorrect injection. > [1] https://c.na7.visual.force.com/apex/Case_View?id=500A000000CRqDG&sfdc.ove... > Version-Release number of selected component (if applicable): > How reproducible: > To reproduce the case is required to have two PersistentUnit (PU), a Abstract class with a setter method to inject one PU and others classes inheriting the Abstract class and overriding the setter method to inject a different PU. In the runtime, the container inject twice the PU, first the correct PU and then the PU described in super class. > I talked with the client (who is a Red Hat consultant) and we made the attached project based on a very simple JBoss example to reproduce the issue which happens in EAP6. I put a lot of 'println' to be very clear (even printing stacktrace to show who is calling). The most important files are: > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/BaseDAO.java -- The abstract class with the default PU injection > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/SecondaryMemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberListProducer.java -- The class which inject the MemberListProducer and SecondaryMemberRepository > -> hibernate4Test/src/main/resources/META-INF/persistence.xml -- We changed the configuration here to each PU have a different entity mapped > Steps to Reproduce: > > Actual results: > The EM injection occurs twice, which the last one the wrong EM. > Expected results: > Just one injection occurs. > Additional info: -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-115) JMSService error during :reload operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-115?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-115: ---------------------------------------------- Nikoleta Ziakova <nziakova(a)redhat.com> made a comment on [bug 951649|https://bugzilla.redhat.com/show_bug.cgi?id=951649] We could not hit this problem neither with EAP 6.1.0 (tried DR4,ER4), nor with EAP 6.0.1. Verified for EAP 6.1.0 ER6. > JMSService error during :reload operation > ----------------------------------------- > > Key: WFLY-115 > URL: https://issues.jboss.org/browse/WFLY-115 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > if the admin client performs a :reload operation, the JMSService throws an exception and HornetQ server is not stopped properly and do not release its resources: > {noformat} > 20:01:54,480 ERROR [org.jboss.messaging] (MSC service thread 1-1) JBAS011602: Exception while stopping JMS server: java.lang.IllegalStateException: Service already removed > at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:792) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:775) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.setMode(ServiceControllerImpl.java:754) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.as.messaging.jms.JMSService$1.deActivate(JMSService.java:103) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > at org.hornetq.core.server.impl.HornetQServerImpl.callDeActiveCallbacks(HornetQServerImpl.java:1374) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:598) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:542) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:509) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:502) [hornetq-jms-server-2.3.0.CR2.jar:] > at org.jboss.as.messaging.jms.JMSService.stop(JMSService.java:119) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2082) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2043) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15] > {noformat} > When the HornetQ server is reloaded, it fails to lock its lock files that were not properly released during stop. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-115) JMSService error during :reload operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-115?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-115: ---------------------------------------------- Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 951649|https://bugzilla.redhat.com/show_bug.cgi?id=951649] from ON_QA to VERIFIED > JMSService error during :reload operation > ----------------------------------------- > > Key: WFLY-115 > URL: https://issues.jboss.org/browse/WFLY-115 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > if the admin client performs a :reload operation, the JMSService throws an exception and HornetQ server is not stopped properly and do not release its resources: > {noformat} > 20:01:54,480 ERROR [org.jboss.messaging] (MSC service thread 1-1) JBAS011602: Exception while stopping JMS server: java.lang.IllegalStateException: Service already removed > at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:792) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.internalSetMode(ServiceControllerImpl.java:775) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.setMode(ServiceControllerImpl.java:754) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.as.messaging.jms.JMSService$1.deActivate(JMSService.java:103) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > at org.hornetq.core.server.impl.HornetQServerImpl.callDeActiveCallbacks(HornetQServerImpl.java:1374) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:598) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:542) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.stop(HornetQServerImpl.java:509) [hornetq-server-2.3.0.CR2.jar:] > at org.hornetq.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:502) [hornetq-jms-server-2.3.0.CR2.jar:] > at org.jboss.as.messaging.jms.JMSService.stop(JMSService.java:119) [jboss-as-messaging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2082) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2043) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15] > {noformat} > When the HornetQ server is reloaded, it fails to lock its lock files that were not properly released during stop. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1312) Restore EJB3 tests that deploy duplicate test deployment

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1312?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-1312: --------------------------------- Summary: Restore EJB3 tests that deploy duplicate test deployment (was: Restore tests that deploy duplicate test deployment) > Restore EJB3 tests that deploy duplicate test deployment > -------------------------------------------------------- > > Key: WFLY-1312 > URL: https://issues.jboss.org/browse/WFLY-1312 > Project: WildFly > Issue Type: Task > Components: EJB > Reporter: Thomas Diesler > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > > There are a number of EJB3 tests that [have been disabled|https://github.com/wildfly/wildfly/commit/a22ea284c7a7761e4626e1...] because they deploy a duplicate test deployment -- 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

13 years, 2 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 May 2013