July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5247) Include the JBoss Negotiation Toolkit in the AS distribution.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5247: ------------------------------------- Summary: Include the JBoss Negotiation Toolkit in the AS distribution. Key: AS7-5247 URL: https://issues.jboss.org/browse/AS7-5247 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 The JBoss Negotiation Toolkit web app is essential when setting up a server to use SPNEGO negotiation as it allows the different steps to be broken down and verified individually. The war should be included in the distribution to make it easily accessible - this will also make sure the toolkit version matches the actual version of JBoss Negotiation in use. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (JGRP-1497) FD_SOCK server socket is never closed after network interruption

by Dennis Reed (JIRA)

Dennis Reed created JGRP-1497: --------------------------------- Summary: FD_SOCK server socket is never closed after network interruption Key: JGRP-1497 URL: https://issues.jboss.org/browse/JGRP-1497 Project: JGroups Issue Type: Bug Affects Versions: 2.6.21 Reporter: Dennis Reed Assignee: Dennis Reed The server side of the FD_SOCK socket is never closed after a network interruption during which the client side is closed. JGRP-195 added TCP keepalive to FD_SOCK, but only to the client side. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] (AS7-3286) Regster InitialContextFactoryBuilder service the the OSGi layer to enable OSGi spec-compliant JNDI integration

by David Bosschaert (JIRA)

David Bosschaert created AS7-3286: ------------------------------------- Summary: Regster InitialContextFactoryBuilder service the the OSGi layer to enable OSGi spec-compliant JNDI integration Key: AS7-3286 URL: https://issues.jboss.org/browse/AS7-3286 Project: Application Server 7 Issue Type: Task Components: Naming Reporter: David Bosschaert Assignee: David Bosschaert Fix For: 7.1.0.Final In order to facilitate integration with the OSGi JNDI specification, an InitialContextFactoryBuilder needs to be registered as an MSC service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (SECURITY-572) Support for situation when first OID is Kerberos OID instead of SPNEGO OID

by Marek Posolda (JIRA)

Support for situation when first OID is Kerberos OID instead of SPNEGO OID -------------------------------------------------------------------------- Key: SECURITY-572 URL: https://issues.jboss.org/browse/SECURITY-572 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Environment: JBoss EPP 5.1.GA with SPNEGO support, JBoss Negotiation 2.0.3, commons-http-client 3.1 used as HTTP client Reporter: Marek Posolda Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4 Currently first byte of SPNEGO token is used to recognize if it's new token NegTokenInit and another 3 bytes are used to recognized length. From byte 5 is starting sequence for recognizing OID. Currently NegotiationAuthenticator is able to handle situations where this OID is SPNEGO OID (1.3.6.1.5.5.2) but it's not able to correctly handle situations where first OID is Kerberos OID (1.2.840.113554.1.2.2). Problem is that if Kerberos is used, then the rest of sequence format is different then for SPNEGO and IOException is thrown in method NegTokenInitDecoder.decodeNegTokenInitSequence because the sequence type is not expected value (any of 0xa0, 0xa1, 0xa2, 0xa3). I think that support for Kerberos OID is not critical and I am not sure if it's really the issue, but guys here https://issues.apache.org/jira/browse/HTTPCLIENT-523 are saying that it's working correctly with IIS but not with JBoss Negotiation. For simulating of situation can be used commons-httpclient3 with integration of NegotiateScheme: http://svn.apache.org/repos/asf/httpcomponents/oac.hc3x/trunk/src/contrib... Or you can simulate it by sending this Negotiate token in HTTP header: Authorization : Negotiate YIID7QYJKoZIhvcSAQICAQBuggPcMIID2KADAgEFoQMCAQ6iBwMFAAAAAACjggEEYYIBADCB/aADAgEFoQ8bDUxPQ0FMLk5FVFdPUkuiJzAloAMCAQChHjAcGwRIVFRQGxRzZXJ2ZXIubG9jYWwubmV0d29ya6OBuzCBuKADAgEDoQMCAQOigasEgajWrIRyQlCHtxXO//EMI/6C9zBChS00QtgZLctUa0qjb14RZFFj5pyruAB7SrqnxuD7JROJpwsVZG7FDpFu47Y3ZXyWjq8C1px+V4CULGgOt3Aufyh8DVRGeuhxYQ17APR5pC418Wo/u/VIJvLco7VZaAlGEF0xyJ8thtBM8Oz88urPpVxOl+7mUd2XirkqReL5ITdsEOjnZ4Q8duYKDPq9GdVcvf7MFyikggK5MIICtaADAgEBooICrASCAqjngVyeX24XzPtoMsnO0W2DoiX+SfpshcbZOVN0ne98Zxhnq3gxxiHiiI3voWTqtAiXe9E/Ti+wPuFI1g4jXsOjY8V4GGfDxihxGSMa9vu45JvLr+MPL40EwmFaD6fRpU+DA80ZhS+1THhTKT2w28pJS45fgSM2igmXQYk0hfv/Q7xIYBmNJXMZ2ZgyY8dek5dflg9zjuZetR6RSYJtu7Q+c/w3t/yHYLtcrz98aD+Q4EjBtf4I3EpP+c5NSkpouSvRy8u4yPNgOyvM8CdXuABveVdl+/DX100ucJc9uXAL+lPMdk+YMo8rAoEWae3km5LDfd3JncPB50OKwjNzejvi5e+5OYG17TpTx88sGMl0JLQ5mgrUBMPMG/c2sje4mhmTa8nO8SdqP6Fa1HVYPZNgDskSvTQzM0zsLRU0tyuge41hB8J6AOje1rGvpLBKMdMbXqnD08aC0N1qL1b5TmNk2jcWyJaGAi1pxzyNDwFTL5LUr7e+bIHrX2nd3g328pdDfZCBiqvrInXR+7phnKYinit22O4ktQQRuS9bybZR+ECAVrnCXspPieIvPLZYrzEDgp3NXYlUUzyWuNBN/obXAHiXhE0LMtnDvSs/MQYHTjGAahoKVjxNWDSmRylGD49dAI/N+cNnB/1NruSTLd5voahGYrnDmoouWafa4oaARZqq48lSAgaMhfPoMfYaBSWS9mWYltBEsTUAQO3sNg0Sx0d0jtQzQG/37mxKCF5F/rAeeI5NQcRrXV1RZzkY7UPyaiIwelt/ZOo2tJqgkSIKQwPBlH/GGlRvrCse3f2Eg/FoSKUMTHkjl433BiG4J9+5Isgchgl6XfolW4d7b5Ztqg0zi+k0ydTzpeK1h9mYbJ1ML2rdlHTXNEnF0fmwz+4SGk09bG/Rqw== Another thing is handling of IOException, which is not logged anywhere, but I will create another JIRA issue for it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] (SECURITY-676) Bring versions in line with current AS 7.1.x branch

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-676: ----------------------------------------- Summary: Bring versions in line with current AS 7.1.x branch Key: SECURITY-676 URL: https://issues.jboss.org/browse/SECURITY-676 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_2_1 The release will be used in both the 7.1.x branch and master but keep in synch with 7.1.x - if we need to diverge we will start a negotiation 2.3 release stream. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4253) TCCL used by EJBNamingContext is wrong when callstack passes through multiple OSGi modules

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4253: ----------------------------------- Summary: TCCL used by EJBNamingContext is wrong when callstack passes through multiple OSGi modules Key: AS7-4253 URL: https://issues.jboss.org/browse/AS7-4253 Project: Application Server 7 Issue Type: Bug Components: EJB, OSGi Reporter: Thomas Diesler Assignee: jaikiran pai Fix For: 7.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
22
0 / 0

[JBoss JIRA] (AS7-5262) Decouple naming & transaction from OSGi

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5262: ----------------------------------- Summary: Decouple naming & transaction from OSGi Key: AS7-5262 URL: https://issues.jboss.org/browse/AS7-5262 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Currently the naming & transaction subsystem register services on behalf of OSGi {code} [tdiesler@tdvaio jboss-as]$ git grep "\"xservice\"" naming/src/main/java/org/jboss/as/naming/subsystem/NamingSubsystemOSGiService.java: ServiceName serviceName = ServiceName.of("jbosgi", "xservice", regi transactions/src/main/java/org/jboss/as/txn/service/TransactionManagerService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", Tran transactions/src/main/java/org/jboss/as/txn/service/UserTransactionService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", UserTra {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3546) Planner: Late acceptance and great deluge get stuck in an endless move iterator loop because there are no acceptable moves

by Geoffrey De Smet (JIRA)

13 years, 11 months

1
4
0 / 0

[JBoss JIRA] (JBJCA-866) Some boolean attributes of DataSources object are proceeded incorrectly in toString() method

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created JBJCA-866: ----------------------------------------- Summary: Some boolean attributes of DataSources object are proceeded incorrectly in toString() method Key: JBJCA-866 URL: https://issues.jboss.org/browse/JBJCA-866 Project: IronJacamar Issue Type: Bug Reporter: Vladimir Rastseluev Assignee: Vladimir Rastseluev Fix For: 1.0.12.Final, 1.1.0.Beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBJCA-865) Missing hashCode() and equals() methods in CommonPoolImpl class

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created JBJCA-865: ----------------------------------------- Summary: Missing hashCode() and equals() methods in CommonPoolImpl class Key: JBJCA-865 URL: https://issues.jboss.org/browse/JBJCA-865 Project: IronJacamar Issue Type: Bug Reporter: Vladimir Rastseluev Assignee: Vladimir Rastseluev Fix For: 1.0.12.Final, 1.1.0.Beta2 All objects using CommonPool as a part of equals() method will never be equals with other object. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
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 July 2012