January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-559) AdvancedLdapLoginModule: Service Principal is not constructed from java.naming.provider.url

by John Ruiz (JIRA)

AdvancedLdapLoginModule: Service Principal is not constructed from java.naming.provider.url ------------------------------------------------------------------------------------------- Key: SECURITY-559 URL: https://issues.jboss.org/browse/SECURITY-559 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Environment: Windows Server 2008 R2 domain controller, Red Hat 5.5 Application Server (JBoss), Windows 7 Clients Reporter: John Ruiz Assignee: Darran Lofthouse Priority: Critical When using org.jboss.security.negotiation.AdvancedLdapLoginModule chained with SPNEGO/Kerberos against Active Directory, the service principal specified in the TGS-REQ is ldap/foo.com, even though java.naming.provider.url is set to LDAP://dc1.foo.com. Because of this, the /Secured test in the jboss-negotiation-toolkit will fail to bind to AD/LDAP because the KDC returns an error KRB5KDC_ERR_S_PRINCIPAL_UNKNOWN. The correct service principal name that the TGS-REQ should request is LDAP/dc1.foo.com because dc1.foo.com is what was provided in java.naming.provider.url. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1845) Remoting configuration parameter adjustment

by Yong Hao Gao (JIRA)

Remoting configuration parameter adjustment ------------------------------------------- Key: JBMESSAGING-1845 URL: https://issues.jboss.org/browse/JBMESSAGING-1845 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP11 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP12, 1.4.8.GA Current remoting config has the following commented:   So defaults for those params will be used, and will turn off pinging on control connection, which would be useful to keep the control connection alive in case of a firewall. So we should uncomment it as the following  <attribute name="numberOfCallRetries" isParam="true">5</attribute> <attribute name="pingFrequency" isParam="true">30000</attribute> <attribute name="pingWindowFactor" isParam="true">71582</attribute> <attribute name="generalizeSocketException" isParam="true">true</attribute> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8828) Enable Weld usage of MC Scanning lib

by Ales Justin (JIRA)

Enable Weld usage of MC Scanning lib ------------------------------------ Key: JBAS-8828 URL: https://issues.jboss.org/browse/JBAS-8828 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.Final Reporter: Ales Justin Assignee: Ales Justin Fix For: 6.0.1 Make Weld use existing Scanning lib, adding a plugin to existing deployment scanning. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-668) Licensing for org.hyperic:sigar dependencies has changed and needs to be updated in poms

by Karla Jacobsen (JIRA)

Licensing for org.hyperic:sigar dependencies has changed and needs to be updated in poms ---------------------------------------------------------------------------------------- Key: JBBUILD-668 URL: https://issues.jboss.org/browse/JBBUILD-668 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Reporter: Karla Jacobsen The licensing for Sigar (versions 1.6.4 and newer) has changed from GPLv3 to Apache 2.0. The poms in the JBoss Thirdparty Uploads repository show the old license. It would be great if this could be corrected in some way -- I'm not sure what the JBoss policy/strategy is for making corrections to the repository. See the links below for documentation about the license change: * http://support.hyperic.com/display/SIGAR/Home#Home-license * http://forums.hyperic.com/jiveforums/thread.jspa?threadID=11426 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8794) AS 6.0 dist zip: File names differing only in letter case

by Ondrej Zizka (JIRA)

AS 6.0 dist zip: File names differing only in letter case --------------------------------------------------------- Key: JBAS-8794 URL: https://issues.jboss.org/browse/JBAS-8794 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi integration Affects Versions: 6.0.0.Final Reporter: Ondrej Zizka Priority: Minor All these files are the same: jboss-6.0.0.Final\docs\licenses\GNU Lesser General Public Licence - lgpl.txt jboss-6.0.0.Final\docs\licenses\GNU LESSER GENERAL PUBLIC LICENSE - lgpl.txt jboss-6.0.0.Final\docs\licenses\GNU Lesser General Public License - lgpl.txt jboss-6.0.0.Final\docs\licenses\GNU Lesser General Public License (LGPL), Version 2.1 - lgpl.txt More, the first two cause error when extracting on Windows since Windows filesystems consider paths differing in letter cases the same paths. I suggest to remove three of the files above. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2234) Clustered @Singleton

by Carlo de Wolf (JIRA)

Clustered @Singleton -------------------- Key: EJBTHREE-2234 URL: https://issues.jboss.org/browse/EJBTHREE-2234 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Fix For: TBD EAP 6 It should be possible to create a clustered singleton by just adding the @Clustered annotation. @Singleton @Clustered public class MyScheduler { } Care should be taken that the life-cycle callbacks are only invoked once on one node, the other nodes will only receive the state of the singleton after post-construct. Concurrency management of the singleton should happen cross-cluster, so that a singleton with read lock can be concurrently invoked on any node. After existing a method with a write lock the state must be synchronized across the cluster before new invocations are processed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1828) Deprecated usage of runtime components during dependency resolve

by Carlo de Wolf (JIRA)

Deprecated usage of runtime components during dependency resolve ---------------------------------------------------------------- Key: EJBTHREE-1828 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1828 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.1.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JASSIST-137) getDeclaringClass() throws IncompatibleClassChangeError on copy of inner class

by Ragnar Rova (JIRA)

getDeclaringClass() throws IncompatibleClassChangeError on copy of inner class ------------------------------------------------------------------------------ Key: JASSIST-137 URL: https://issues.jboss.org/browse/JASSIST-137 Project: Javassist Issue Type: Bug Affects Versions: 3.14.0.GA Environment: sun jdk1.6.0_21 Reporter: Ragnar Rova Assignee: Shigeru Chiba Creating a copy of a inner class and then calling getDeclaringClass() on the copied class causes error. How to create a copy of such a class? java.lang.IncompatibleClassChangeError: foo.GetDeclaringClassTest and foo.GetDeclaringClassTest$Foo$BackRef disagree on InnerClasses attribute at java.lang.Class.getDeclaringClass(Native Method) at foo.GetDeclaringClassTest.get_declaring_class_should_not_throw_error(GetDeclaringClassTest.java:20) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (LOGTOOL-9) Generics are being in import declarations

by James Perkins (JIRA)

Generics are being in import declarations ----------------------------------------- Key: LOGTOOL-9 URL: https://issues.jboss.org/browse/LOGTOOL-9 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.0.Beta3 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-1197) ConnectionTable: trash it

by Bela Ban (JIRA)

ConnectionTable: trash it ------------------------- Key: JGRP-1197 URL: https://jira.jboss.org/jira/browse/JGRP-1197 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 This class isn't used anymore; we use ConnectionMap instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011