May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-749) Expose useSynchronization from infinispan subsystem schema

by Paul Ferraro (JIRA)

Expose useSynchronization from infinispan subsystem schema ---------------------------------------------------------- Key: AS7-749 URL: https://issues.jboss.org/browse/AS7-749 Project: Application Server 7 Issue Type: Enhancement Components: Clustering Affects Versions: 7.0.0.Beta3 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.0.0.CR1 By default, useSynchronization should be true. Add schema option to disable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-591) Single security domain with DatabaseSourceLoginModule and DatabaseCertLoginModule only works if allowUnsafeLegacyRenegotiation="true"

by Justin Cranford (JIRA)

Single security domain with DatabaseSourceLoginModule and DatabaseCertLoginModule only works if allowUnsafeLegacyRenegotiation="true" ------------------------------------------------------------------------------------------------------------------------------------- Key: SECURITY-591 URL: https://issues.jboss.org/browse/SECURITY-591 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_CR2 Environment: Windows 7 Enterprise x64 Eclipse EE 3.6.2 Oracle JDK 6u24 JBoss 6.0 AS Final (PicketBox 3.0.0CR2) SQL Server Express 2008 R2 x64 Reporter: Justin Cranford Assignee: Anil Saldhana I am blocked by broken functionality in JBossSX login modules. The functionality is broken because SSL renegotiation is disabled. Disabling SSL renegotiation is valid, but is it possible to fix or workaround the login module issue without enabling SSL renegotiation? - I posed this question on the PicketBox forum, but perhaps it belongs here instead. http://community.jboss.org/message/604544#604544 - I get similar exceptions in Resteasy as what this person reported in SOAP. https://issues.jboss.org/browse/JBPAPP-3889 - The original issue to disable SSl renegotiation by default is tracked by this issue, and it mentions how functionality might break. However, there is no mention of potential workarounds or fixes. https://issues.jboss.org/browse/JBPAPP-3845 My requirements are to support Resteasy web access over HTTPS using one of 2 authentication methods. For localhost access, user/pass authentication is sufficient. For remote access, X.509 client cert authentication is required. To implement these requirements, I deployed two nearly identical Resteasy web apps. The only differences are the context path in jboss-web.xml, and <auth-constraint> and <auth-method> in web.xml. 1) localhost HTTPS web app => username/password (LocalAdmin role only) <login-config><auth-method>BASIC</auth-method><realm-name>JustinCranfordSecurityDomain</realm-name></login-config> <security-role><role-name>LocalAdmin</role-name></security-role> 2) remote HTTPS => x.509 client cert (RemoteAdmin role only) <login-config><auth-method>CLIENT-CERT</auth-method><realm-name>JustinCranfordSecurityDomain</realm-name></login-config> <security-role><role-name>RemoteAdmin</role-name></security-role> Both web apps are wrappers for the same EJB3 code, so I am forced to combine DatabaseServerLoginModule and DatabaseCertLoginModule into the same <application-policy> in login-config.xml. <application-policy name="JustinCranfordSecurityDomain"> <authentication> <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="sufficient"> <module-option name="dsJndiName">java:/JustinCranfordDataSource</module-option> <module-option name="principalsQuery">SELECT password FROM actor WHERE name=?</module-option> <module-option name="rolesQuery">SELECT r.name,'Roles' FROM actor a,role r WHERE r.id=a.roleid AND a.name=?</module-option> <module-option name="hashAlgorithm">MD5</module-option> <module-option name="hashEncoding">base64</module-option> <module-option name="unauthenticatedIdentity">unauthenticated</module-option> </login-module> <login-module code="org.jboss.security.auth.spi.DatabaseCertLoginModule" flag="required"> <module-option name="securityDomain">java:/jaas/JustinCranfordSecurityDomain</module-option> <module-option name="dsJndiName">java:/JustinCranfordDataSource</module-option> <module-option name="principalsQuery">SELECT password FROM actor WHERE dname=?</module-option> <module-option name="rolesQuery">SELECT r.name,'Roles' FROM actor a,role r WHERE r.id=a.roleid AND a.dname=?</module-option> <module-option name="hashAlgorithm">MD5</module-option> <module-option name="hashEncoding">base64</module-option> <module-option name="unauthenticatedIdentity">unauthenticated</module-option> </login-module> <login-module code="org.jboss.security.ClientLoginModule" flag="required"></login-module> </authentication> </application-policy> DatabaseCertLoginModule only works if my web app turns on SSL renegotiation in server.xml via the allowUnsafeLegacyRenegotiation="true" attribute. If turned off, I get SSL renegotiation disabled messages in JBossSX login modules. However, DatabaseCertLoginModule says the user is authenticated, and I see "Successfully passed all security constraints". Unfortunately JBossWebRealm then throws an exception "Security Context has not been set", control passes to Resteasy, and then "jboss.web" container throws an exception "Exception getting SSL attributes: java.net.SocketException: Socket Closed" and "No certificates included with this request". At the very least, JBossSX should handle these problems more gracefully. SSL renegotiation is disabled by default after all. Is is possible to fix these issues in JBossSX? Are there any workarounds in the meantime? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3020) droolsjbpm-integration example does not compile in Eclipse

by Jervis Liu (JIRA)

droolsjbpm-integration example does not compile in Eclipse ---------------------------------------------------------- Key: JBRULES-3020 URL: https://issues.jboss.org/browse/JBRULES-3020 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M2 Reporter: Jervis Liu Assignee: Mark Proctor Priority: Critical Fix For: 5.2.0.CR1 droolsjbpm-integration example does not compile in Eclipse. How to reproduce: 1. download droolsjbpm-integration distribution from https://hudson.qa.jboss.com/hudson/view/Drools%20jBPM/job/droolsjbpm-inte... 2. build examples using the pom provided: mvn eclipse:eclipse 3. Import project into Eclipse 4. There are 323 errors in Eclipse -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3016) The screen shot in "Drools Expert User Guide" section 8.3 is out-of-date.

by Jervis Liu (JIRA)

The screen shot in "Drools Expert User Guide" section 8.3 is out-of-date. -------------------------------------------------------------------------- Key: JBRULES-3016 URL: https://issues.jboss.org/browse/JBRULES-3016 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M2 Reporter: Jervis Liu Assignee: Mark Proctor Fix For: 5.2.0.CR1 The screen shot in "Drools Expert User Guide" section 8.3 is out-of-date. Attached is the screen shot from the latest version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3015) Please update "Drools Expert User Guide" Chapter 8. The Rule IDE (Eclipse), to doc how to add a new Drools runtime.

by Jervis Liu (JIRA)

Please update "Drools Expert User Guide" Chapter 8. The Rule IDE (Eclipse), to doc how to add a new Drools runtime. -------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3015 URL: https://issues.jboss.org/browse/JBRULES-3015 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.2.0.M2 Reporter: Jervis Liu Assignee: Mark Proctor Fix For: 5.2.0.CR1 Please update "Drools Expert User Guide" Chapter 8. The Rule IDE (Eclipse), to doc how to add a new Drools runtime. This can be confusing for new users. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (AS7-673) Intermittent smoke test failures in embedded.osgi package

by Brian Stansberry (JIRA)

Intermittent smoke test failures in embedded.osgi package --------------------------------------------------------- Key: AS7-673 URL: https://issues.jboss.org/browse/AS7-673 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Brian Stansberry Assignee: Jason Greene Scott Marlow and I seeing intermittent failures in the smoke tests in the embedded.osgi package: SimpleDeploymentProviderTestCase or SimpleArchiveDeployerTestCase. I'll attach representative test output. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
4
0 / 0

[JBoss JIRA] Created: (AS7-745) Upgrade to JBossWS-CXF 4.0.0.Beta1

by Alessio Soldano (JIRA)

Upgrade to JBossWS-CXF 4.0.0.Beta1 ---------------------------------- Key: AS7-745 URL: https://issues.jboss.org/browse/AS7-745 Project: Application Server 7 Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.0.0.CR1 Move to jbossws cxf 4.0.0.Beta1 including its dependencies. Also move from jaxws-httpserver-httpspi to jaxws-jboss-httpserver-httpspi as a consequence of recent move from com.sun.net.httpserver to org.jboss.com.sun.httpserver. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[JBoss JIRA] Created: (JBWEB-199) Fix empty string to number conversion

by Mike Millson (JIRA)

Fix empty string to number conversion ------------------------------------- Key: JBWEB-199 URL: https://issues.jboss.org/browse/JBWEB-199 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Reporter: Mike Millson Assignee: Mike Millson EL expression parser error when getter method returns an empty string. Fix empty string to number conversion. Reference: https://issues.apache.org/bugzilla/show_bug.cgi?id=47371 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3023) The Audit view in Drools Eclipse plugin does not work

by Jervis Liu (JIRA)

The Audit view in Drools Eclipse plugin does not work ----------------------------------------------------- Key: JBRULES-3023 URL: https://issues.jboss.org/browse/JBRULES-3023 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-eclipse Affects Versions: 5.2.0.M2 Reporter: Jervis Liu Assignee: Mark Proctor Fix For: 5.2.0.CR1 The Audit view in Drools Eclipse plugin does not work. Or maybe it is sth wrong with the logger. How to reproduce: 1. download drools distribution from https://hudson.qa.jboss.com/hudson/view/Drools%20jBPM/job/drools-5.2.x/3/ 2. Build example using pom provided: mvn clean install 3. Generate Eclipse project: mvn eclipse:eclipse 4. Import example project into Eclipse. 5. Set a break point in Helloworld.drl. Uncomment the logger in HelloWorldExample.java 6. Debug HelloWorldExample as Drools 7. There is nothing showed up in Audit view. And there is an exception in console: Exception in thread "main" java.lang.RuntimeException: Could not create the log file. Please make sure that directory that the log file should be placed in does exist. at org.drools.audit.WorkingMemoryFileLogger.initializeLog(WorkingMemoryFileLogger.java:148) at org.drools.audit.WorkingMemoryFileLogger.writeToDisk(WorkingMemoryFileLogger.java:113) at org.drools.audit.KnowledgeRuntimeLoggerProviderImpl$KnowledgeRuntimeFileLoggerWrapper.close(KnowledgeRuntimeLoggerProviderImpl.java:56) at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:81) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2907) Replace license header in all files with standarized jbossorg ASL license header

by Geoffrey De Smet (JIRA)

Replace license header in all files with standarized jbossorg ASL license header -------------------------------------------------------------------------------- Key: JBRULES-2907 URL: https://issues.jboss.org/browse/JBRULES-2907 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Toni Rikkola Priority: Minor Fix For: FUTURE We should follow: http://community.jboss.org/wiki/CopyrightOwnershipandLicenses -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011