June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3554) drools-server 5.0.1 - cannot pull in rulebases from guvnor >5.2 when authentication is enabled

by Nicholas DiPiazza (JIRA)

Nicholas DiPiazza created JBRULES-3554: ------------------------------------------ Summary: drools-server 5.0.1 - cannot pull in rulebases from guvnor >5.2 when authentication is enabled Key: JBRULES-3554 URL: https://issues.jboss.org/browse/JBRULES-3554 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.0.FINAL Environment: All OS - only Drools Server 5.0.x connecting to Guvnor > 5.2 with some sort of authentication turned on with security:identity in components.xml Reporter: Nicholas DiPiazza Assignee: Mark Proctor There is an issue in org.drools.agent.HttpClientImpl.checkLastUpdated(URL u) When the URL passed in is not guest accessible (requires basic authentication), this is not a handled situation in this version of Drools. So when you try to use Drools Execution Server to connect rulebase in Guvnor >5.2 (has authentication enabled)... it will fail if the rulebase URL is not guest accessible. These two methods need to have authentication added in (marked by START and END NDD). public LastUpdatedPing checkLastUpdated(URL url) throws IOException { URLConnection con = url.openConnection(); HttpURLConnection httpCon = (HttpURLConnection) con; try { // **** START NDD ***** BASE64Encoder enc = new sun.misc.BASE64Encoder(); String userpassword = "ad-user" + ":" + "ad-password"; String encodedAuthorization = enc.encode( userpassword.getBytes() ); httpCon.setRequestProperty("Authorization", "Basic "+ encodedAuthorization); // **** END NDD ***** httpCon.setRequestMethod( "HEAD" ); String lm = httpCon.getHeaderField( "lastModified" ); LastUpdatedPing ping = new LastUpdatedPing(); ping.responseMessage = httpCon.getHeaderFields().toString(); if ( lm != null ) { ping.lastUpdated = Long.parseLong( lm ); } else { long httpLM = httpCon.getLastModified(); if ( httpLM > 0 ) { ping.lastUpdated = httpLM; } } return ping; } finally { httpCon.disconnect(); } } public Package fetchPackage(URL url) throws IOException, ClassNotFoundException { URLConnection con = url.openConnection(); HttpURLConnection httpCon = (HttpURLConnection) con; try { // **** START NDD ***** BASE64Encoder enc = new sun.misc.BASE64Encoder(); String userpassword = "ad-user" + ":" + "ad-password"; String encodedAuthorization = enc.encode( userpassword.getBytes() ); httpCon.setRequestProperty("Authorization", "Basic "+ encodedAuthorization); // **** END NDD ***** httpCon.setRequestMethod( "GET" ); Object o = DroolsStreamUtils.streamIn( httpCon.getInputStream() ); if ( o instanceof KnowledgePackageImp ) { return ((KnowledgePackageImp) o).pkg; } else { return (Package) o; } } finally { httpCon.disconnect(); } } Obviously a production scenario would pull those username/password combinations from the .properties file for the rulebase. -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] (AS7-4017) CLI --commands attribute don't work with comma separated

by Samuel Tauil (JIRA)

Samuel Tauil created AS7-4017: --------------------------------- Summary: CLI --commands attribute don't work with comma separated Key: AS7-4017 URL: https://issues.jboss.org/browse/AS7-4017 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Final Environment: I'm using fedora 16 and java.1.6.0_25. JBoss AS 7 Final 7.1.0 Reporter: Samuel Tauil Assignee: Alexey Loubyansky When I try to execute multiple commands in CLI using the script I got an error. The parameter --commands of the jboss-cli.sh seems to do a string split by comma, but are commands that use comma as character to separate attributes. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] (AS7-4630) add-user script broken

by Dustin Kut Moy Cheung (JIRA)

Dustin Kut Moy Cheung created AS7-4630: ------------------------------------------ Summary: add-user script broken Key: AS7-4630 URL: https://issues.jboss.org/browse/AS7-4630 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Dustin Kut Moy Cheung Assignee: Dustin Kut Moy Cheung ./add-user.sh dustin dustin1 does not work anymore. In previous versions it would work. It has to do with the "theConsole" object being null. In the same breadth, the --silent=true option in add-user.sh does not work anymore. Again has to do with the need for "theConsole" object NOT being null. The --silent=true option was added because in some environments, System.console() returns null [for example when the Izpack installer calls that script] and the add-user.sh script breaks because of its dependence on System.console() object to print stuff. -- 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, 10 months

3
13
0 / 0

[JBoss JIRA] (JBRULES-3545) Support declarative configuration for knowledge runtime loggers (console, file, threaded-file)

by Vinod Kiran Paidimarry (JIRA)

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] (AS7-4932) CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation

by Michael Nielson (JIRA)

[ https://issues.jboss.org/browse/AS7-4932?page=com.atlassian.jira.plugin.s... ] Michael Nielson commented on AS7-4932: -------------------------------------- My understanding is that passivation is the default for AS-7, can I workaround this bug with: <file-store shared="false" passivation="false"/> > CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation > ------------------------------------------------------------------------------------------------------------- > > Key: AS7-4932 > URL: https://issues.jboss.org/browse/AS7-4932 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 7.1.3.Final (EAP) > > > NPE is thrown in roughly 0.36% of HTTP session request processing in the test. > This results in response code 503 returned to the client with the exception. > The test is using passivation-enabled WAR of clusterbench > https://github.com/rhusar/clusterbench > Here is a shorter soak test run that uncovered the issue > https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Clustering-Soak/jo... > {noformat} > [JBossINF] 19:52:10,113 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-2570) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.NullPointerException > [JBossINF] at org.jboss.as.web.session.ClusteredSession.update(ClusteredSession.java:972) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1377) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:673) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:84) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.apache.catalina.connector.Request.doGetSession(Request.java:2618) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:841) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.getSession(LazySessionBeanStore.java:72) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.<init>(LazySessionBeanStore.java:58) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:31) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:16) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:134) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:452) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > {noformat} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-4984) Exclusion of Modules does not work with EAR to EAR communication

by Sebastian Woeste (JIRA)

13 years, 10 months

4
13
0 / 0

[JBoss JIRA] (AS7-5058) Integrate JGroups ENCRYPT with AS security infrastructure

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5058: ------------------------------------- Summary: Integrate JGroups ENCRYPT with AS security infrastructure Key: AS7-5058 URL: https://issues.jboss.org/browse/AS7-5058 Project: Application Server 7 Issue Type: Sub-task Components: Clustering, Security Reporter: Brian Stansberry Assignee: Paul Ferraro Integrate JGroups ENCRYPT (or some similar protocol) with the AS security infrastructure, such that redundant configuration of keystore information is avoided. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5057) Integrate JGroups AUTH with AS security infrastructure

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5057: ------------------------------------- Summary: Integrate JGroups AUTH with AS security infrastructure Key: AS7-5057 URL: https://issues.jboss.org/browse/AS7-5057 Project: Application Server 7 Issue Type: Sub-task Components: Clustering, Security Reporter: Brian Stansberry Assignee: Paul Ferraro Integrate JGroups AUTH (or some similar protocol) with the AS security realm infrastructure, such that the credentials needed for a peer to authenticate can come from the realm and be verified by the realm. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5056) Integrate JGroups diagnostics with AS security

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5056: ------------------------------------- Summary: Integrate JGroups diagnostics with AS security Key: AS7-5056 URL: https://issues.jboss.org/browse/AS7-5056 Project: Application Server 7 Issue Type: Sub-task Components: Clustering, Security Reporter: Brian Stansberry Assignee: Paul Ferraro Integrate JGroups diagnostics with AS security, such that probe.sh users can provide credentials allowing them to authenticate against the AS security realm used for securing other management interfaces. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5055) Integrate JGroups with core AS security infrastructure

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5055: ------------------------------------- Summary: Integrate JGroups with core AS security infrastructure Key: AS7-5055 URL: https://issues.jboss.org/browse/AS7-5055 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, Security Reporter: Brian Stansberry Assignee: Paul Ferraro Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- 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, 10 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 June 2012