January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2553) CompositeSelector should support weighting the selection of each sub selector.

by Geoffrey De Smet (JIRA)

CompositeSelector should support weighting the selection of each sub selector. ------------------------------------------------------------------------------ Key: JBRULES-2553 URL: https://jira.jboss.org/browse/JBRULES-2553 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.1.0.M2 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: FUTURE Before the simulated annealing support refactor, this was possible, now it's not because the new CompositeSelector weights them all the same. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9023) EJB Timers

by David Lloyd (JIRA)

EJB Timers ---------- Key: JBAS-9023 URL: https://issues.jboss.org/browse/JBAS-9023 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 Parent task for EJB Timer implementation items. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (SECURITY-610) The continuation of SPNEGO requests causes a 'Login failure' error to be reported.

by Darran Lofthouse (JIRA)

The continuation of SPNEGO requests causes a 'Login failure' error to be reported. ---------------------------------------------------------------------------------- Key: SECURITY-610 URL: https://issues.jboss.org/browse/SECURITY-610 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.0 The continuation from the login module now causes the following error to be logged: - 12:46:42,245 ERROR [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--10.36.4.52-8080-1) Login failure: javax.security.auth.login.LoginException: Continuation Required. at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:174) [jboss-negotiation-2.2.0.SNAPSHOT.jar:2.2.0.SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) [:1.6.0_24] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [:1.6.0_24] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [:1.6.0_24] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_24] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [:1.6.0_24] at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [:1.6.0_24] at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:411) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:154) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:127) [jboss-as-web-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] at org.jboss.security.negotiation.NegotiationAuthenticator.authenticate(NegotiationAuthenticator.java:187) [jboss-negotiation-2.2.0.SNAPSHOT.jar:2.2.0.SNAPSHO Bringing Kerberos to the domain management security is going to require some of the same behaviour as we have in the SPNEGOLoginModule - it may make sense to pull this common behaviour out of the login module anyway for consistency - this would also remove the exception being logged here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] (JBADMCON-165) Admin console uses fixed width

by Rico Neubauer (JIRA)

Rico Neubauer created JBADMCON-165: -------------------------------------- Summary: Admin console uses fixed width Key: JBADMCON-165 URL: https://issues.jboss.org/browse/JBADMCON-165 Project: JBoss Admin Console Issue Type: Bug Components: General Console Affects Versions: 1.0 alpha Environment: Any web-browser Reporter: Rico Neubauer With long deployment names, the fixed width of 816 pixels is too narrow, please see attached screenshots. Fix is simple, just use prozentual widths. I will send a pull request. -- 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, 9 months

2
21
0 / 0

[JBoss JIRA] (AS7-2534) JSF "View could not be restored" if cookies disabled in browser

by Marek Schmidt (Created) (JIRA)

JSF "View could not be restored" if cookies disabled in browser --------------------------------------------------------------- Key: AS7-2534 URL: https://issues.jboss.org/browse/AS7-2534 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.1.0.Alpha1, 7.0.2.Final Environment: JBossAS 7.1.0.Alpha2-SNAPSHOT from 2011-11-07, firefox 3.6.23, Google Chrome 15.0.874.106 Reporter: Marek Schmidt Assignee: Stan Silvert Attachments: jboss-as-numberguess-nocdi.war A JSF application doesn't work if cookies are disabled in browser. The same WAR works on AS6. The generated front page of the app contains `action="/jboss-as-numberguess-nocdi/home.jsf"' attribute in the form element on AS7, while it does contain `/jboss-as-numberguess-nocdi/home.jsf;jsessionid=835F17A..."' on AS 6.1.0. Submitting a form in the app returns HTTP 500 and logs the following exception: 15:14:54,932 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-as-numberguess-nocdi].[Faces Servlet]] (http-localhost.localdomain-127.0.0.1-8080-2) Servlet.service() for servlet Faces Servlet threw exception: javax.faces.application.ViewExpiredException: viewId:/home.jsf - View /home.jsf could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:205) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:155) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] -- 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, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (SECURITY-129) Client Delegation

by Darran Lofthouse (JIRA)

Client Delegation ----------------- Key: SECURITY-129 URL: http://jira.jboss.com/jira/browse/SECURITY-129 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Web browser can delegate to the server being called so same credentials can be used for further calls. Delegation using GSSAPI, WS-Kerberos, credential propagation for EJB calls etc.. -- 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

13 years, 9 months

2
13
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, 9 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, 9 months

2
5
0 / 0

[JBoss JIRA] (AS7-3491) Hornetq address settings reference non-existing DLQ

by Robert Reimann (JIRA)

Robert Reimann created AS7-3491: ----------------------------------- Summary: Hornetq address settings reference non-existing DLQ Key: AS7-3491 URL: https://issues.jboss.org/browse/AS7-3491 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1b Reporter: Robert Reimann Assignee: Andy Taylor The hornetq address-settings inside standalone-full.xml and domain.xml reference a non-existing dead-letter-address "jms.queue.DLQ". See forum reference for details. -- 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, 9 months

5
11
0 / 0

[JBoss JIRA] (AS7-2142) CLI: missing :remove-attribute command

by Rostislav Svoboda (Created) (JIRA)

CLI: missing :remove-attribute command -------------------------------------- Key: AS7-2142 URL: https://issues.jboss.org/browse/AS7-2142 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Rostislav Svoboda Assignee: Alexey Loubyansky Fix For: 7.1.0.CR1 We have _:read-attribute_ and _:write-attribute_ commands but we do not have *:remove-attribute* command. It would be invoked on attributes which have flag required set to false. For example when I define socket-binding-port-offset for server-group I can't remove it and I can't set it to 0 using CLI. {code} /server-group=main-server-group:read-resource-description() "socket-binding-port-offset" => { "description" => "The default offset to be added to the port values given by the socket binding group.", "type" => INT, "required" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {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, 9 months

13
19
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 January 2012