November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-145) Review supported Mech types - currently only Kerberos V5

by Darran Lofthouse (JIRA)

Review supported Mech types - currently only Kerberos V5 -------------------------------------------------------- Key: SECURITY-145 URL: http://jira.jboss.com/jira/browse/SECURITY-145 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse e.g. Should and could we support Kerberos V5 legacy? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
7
0 / 0

[JBoss JIRA] Created: (SECURITY-356) Log a meaningful error when browser uses Kerberos5 GSSAPI and not SPNEGO

by Darran Lofthouse (JIRA)

Log a meaningful error when browser uses Kerberos5 GSSAPI and not SPNEGO ------------------------------------------------------------------------ Key: SECURITY-356 URL: https://jira.jboss.org/jira/browse/SECURITY-356 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA This can be identified by checking the OID parsed in NegTokenInitDecoder.decode() and verifying that it is the OID for SPNEGO. -- 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

14 years

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2623) Decouple window definitions from pattern matching, allowing windows to be reused among various patterns/rules

by Edson Tirelli (JIRA)

Decouple window definitions from pattern matching, allowing windows to be reused among various patterns/rules ------------------------------------------------------------------------------------------------------------- Key: JBRULES-2623 URL: https://jira.jboss.org/browse/JBRULES-2623 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-compiler (fusion), drools-core (fusion) Affects Versions: 5.1.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: FUTURE Decouple window definitions from pattern matching, allowing windows to be reused among various patterns/rules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2634) Design and define semantics for event abstraction. Add syntax sugar for it.

by Edson Tirelli (JIRA)

Design and define semantics for event abstraction. Add syntax sugar for it. --------------------------------------------------------------------------- Key: JBRULES-2634 URL: https://jira.jboss.org/browse/JBRULES-2634 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: FUTURE Design and define semantics for event abstraction. Add syntax sugar for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2633) Design and define execution semantics of event sequencing

by Edson Tirelli (JIRA)

Design and define execution semantics of event sequencing --------------------------------------------------------- Key: JBRULES-2633 URL: https://jira.jboss.org/browse/JBRULES-2633 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: FUTURE Design and define execution semantics of event sequencing: strict, non-strict, pattern repetition, followed-by operator, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2639) Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic

by Edson Tirelli (JIRA)

Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic ---------------------------------------------------------------------------------------------------------- Key: JBRULES-2639 URL: https://jira.jboss.org/browse/JBRULES-2639 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 5.1.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: FUTURE Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
3
0 / 0

[JBoss JIRA] Created: (LOGMGR-24) Bad level "OFF" when using JDK7

by Jesper Pedersen (JIRA)

Bad level "OFF" when using JDK7 ------------------------------- Key: LOGMGR-24 URL: https://jira.jboss.org/browse/LOGMGR-24 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.2.0.CR6 Reporter: Jesper Pedersen Assignee: David Lloyd When using JDK7 I get Caused by: java.lang.ExceptionInInitializerError at sun.util.logging.PlatformLogger.<init>(PlatformLogger.java:164) at sun.util.logging.PlatformLogger.getLogger(PlatformLogger.java:128) at sun.net.www.protocol.http.HttpURLConnection.<clinit>(HttpURLConnection.java:298) at sun.net.www.protocol.http.Handler.openConnection(Handler.java:62) at sun.net.www.protocol.http.Handler.openConnection(Handler.java:57) at java.net.URL.openConnection(URL.java:969) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:628) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1292) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1259) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:260) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1169) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1065) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:978) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:551) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1234) at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:114) at org.jboss.jca.common.metadata.MetadataFactory.getStandardMetaData(MetadataFactory.java:105) at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:166) ... 26 more Caused by: java.lang.IllegalArgumentException: Bad level "OFF" at java.util.logging.Level.parse(Level.java:355) at java.util.logging.LoggingProxyImpl.parseLevel(LoggingProxyImpl.java:95) at sun.util.logging.LoggingSupport.parseLevel(LoggingSupport.java:134) at sun.util.logging.PlatformLogger$JavaLogger.getLevelObjects(PlatformLogger.java:504) at sun.util.logging.PlatformLogger$JavaLogger.<clinit>(PlatformLogger.java:496) ... 46 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-8390) Allow for configuration of respawn policy in host.xml/domain.xml

by Kabir Khan (JIRA)

Allow for configuration of respawn policy in host.xml/domain.xml ---------------------------------------------------------------- Key: JBAS-8390 URL: https://jira.jboss.org/browse/JBAS-8390 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 7.0.0.M1 The server manager currently uses the default respawn policy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-5900) jars are not loaded from the lib directory of a sar in JBoss AS 5

by Matt Wringe (JIRA)

jars are not loaded from the lib directory of a sar in JBoss AS 5 ----------------------------------------------------------------- Key: JBAS-5900 URL: https://jira.jboss.org/jira/browse/JBAS-5900 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.0.0.CR2 Reporter: Matt Wringe Assignee: Scott M Stark Attachments: testsar.tar.gz In JBoss AS 5, any jars placed in the lib directory of a sar are not loaded and results in a class not found exception. The classes are loaded if the jar is placed in the root directory of the sar. On previous versions of JBoss AS, the classes would be loaded from either location. This prevents sars that would have worked on JBoss AS 4 to fail on JBoss AS 5. Steps to reproduce: 1) take zip attached to this report. 2) deploy test-in-lib.sar to JBoss AS 5. The sar will not deploy and will fail with a classNotFoundException 3) deploy test-in-lib.sar to JBoss AS 4, the sar will deploy without issue. test-in-root.sar will work on both versions of JBoss. The only difference between these sars is the location of the jar. -- 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

14 years

5
9
0 / 0

[JBoss JIRA] Created: (SECURITY-542) Add Full Kerberos Support for EJB3 Invocations

by Darran Lofthouse (JIRA)

Add Full Kerberos Support for EJB3 Invocations ---------------------------------------------- Key: SECURITY-542 URL: https://jira.jboss.org/browse/SECURITY-542 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Add full Kerberos support for EJB3 invocations. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
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 November 2010