April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-825) useFirstPass is registered as module option in AbstractServerLoginModule

by Josef Cacek (JIRA)

Josef Cacek created SECURITY-825: ------------------------------------ Summary: useFirstPass is registered as module option in AbstractServerLoginModule Key: SECURITY-825 URL: https://issues.jboss.org/browse/SECURITY-825 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_4_0_19.SP5 Reporter: Josef Cacek Assignee: Josef Cacek useFirsPass is used in {{AbstractServerLoginModule.ALL_VALID_OPTIONS}} array which contains allowed module option names. But the "useFirstPass" is not an option name, it's an option value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1832) Update McastSenderTest/McastReceiverTest to bind the multicast sockets the same as JGroups

by Dennis Reed (JIRA)

Dennis Reed created JGRP-1832: --------------------------------- Summary: Update McastSenderTest/McastReceiverTest to bind the multicast sockets the same as JGroups Key: JGRP-1832 URL: https://issues.jboss.org/browse/JGRP-1832 Project: JGroups Issue Type: Feature Request Affects Versions: 3.4.3 Reporter: Dennis Reed Assignee: Dennis Reed JGroups binds multicast sockets using specific MulticastSocket constructors depending on the operating system (to avoid crosstalk issues). McastSenderTest and McastReceiverTest always bind the socket using the basic MulticastSocket(port) constructor. In order to more closely test the way JGroups will be sending and receiving the packets, these tests will be updated to bind the sockets the same way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-825) useFirstPass is registered as module option in AbstractServerLoginModule

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-825?page=com.atlassian.jira.plug... ] Josef Cacek updated SECURITY-825: --------------------------------- Priority: Minor (was: Major) > useFirstPass is registered as module option in AbstractServerLoginModule > ------------------------------------------------------------------------ > > Key: SECURITY-825 > URL: https://issues.jboss.org/browse/SECURITY-825 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: PicketBox_4_0_19.SP5 > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Minor > > useFirsPass is used in {{AbstractServerLoginModule.ALL_VALID_OPTIONS}} array which contains allowed module option names. But the "useFirstPass" is not an option name, it's an option value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3292) EE Resource Definition Code Rework

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-3292: ------------------------------------- Summary: EE Resource Definition Code Rework Key: WFLY-3292 URL: https://issues.jboss.org/browse/WFLY-3292 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: EE, JCA, JMS, Mail, Naming Reporter: Eduardo Martins Assignee: Eduardo Martins This enhancement task provides a refresh/cleanup of all code related with EE resource definitions (as defined by EE.5.18). A major goal is to sync the logic that works out the deployment of all resource definitions (datasource, connection factory, administered objects, mail session, jms destination and jms connection factory), introducing specific abstract processors for both descriptors and annotations. These processors should continue to use the same functionality under the hood, i.e. feed BindingConfigurations to the same collections as any resource, but may allow in the future an easy split of deployment phase to install the related bindings, which should help the logic of dependent services. Another goal is to fix or provide missing functionality, such as support for <connection-factory /> and <administired-object />. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3290) Cannot use a cluster name other than "ejb"

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-3290?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on WFLY-3290: ---------------------------------------- I've done a short test with former versions. Looks like the issue is in Beta2, I've used Beta2-SNAPSHOT from Nov.2013 and this was working, SNAPSHOT from Dec and later didn't. > Cannot use a cluster name other than "ejb" > ------------------------------------------ > > Key: WFLY-3290 > URL: https://issues.jboss.org/browse/WFLY-3290 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Chris Stillwell > Assignee: Paul Ferraro > Priority: Critical > Attachments: helloworld-test.zip > > > When deploying a clustered session bean the cluster will form only if the cluster name is "ejb". If the standalone-ha.xml is modified to use a different cluster name then the cluster will not form. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3291) Pass Jandex CompositeIndex into Hibernate 5.x

by Scott Marlow (JIRA)

Scott Marlow created WFLY-3291: ---------------------------------- Summary: Pass Jandex CompositeIndex into Hibernate 5.x Key: WFLY-3291 URL: https://issues.jboss.org/browse/WFLY-3291 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 9.0.0.CR1 1. When creating the persistence unit for Hibernate 5.x, pass a Jandex composite index via: integrationMap.put( "hibernate.jandex_index", CompositeIndex.create( pu.getAnnotationIndex().values() ). 2. Also change from: integerationMap.put( "hibernate.ejb.resource_scanner", HibernateArchiveScanner.class ) To: integrationMap.put( "hibernate.jpa.scanner_archive_delegate", VirtualFileSystemArchiveDescriptorFactory.INSTANCE ) This may turn out to be a Jipajapa only change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-472) Drools Eclipse plugin can't recognize third party classes

by Jinghai Rao (JIRA)

Jinghai Rao created DROOLS-472: ---------------------------------- Summary: Drools Eclipse plugin can't recognize third party classes Key: DROOLS-472 URL: https://issues.jboss.org/browse/DROOLS-472 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: * OS: Mac OS X 10.9.2 * Eclipse Kepler * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final) * Java SE 1.7 * Drools Runtime 6.0.1 Reporter: Jinghai Rao Assignee: Mark Proctor Whenever I use classes from any third party jar files (not in JRE System Library and Drools Library), I got error messages in Eclipse IDE. At the place where I import the class, the error message is "Only a type can be imported. ... resolves to a package". At the place where I use the class, the error message is "... cannot be resolved to a type". However, I have included the jar file in classpath. The project can also be executed successfully even with the error message in IDE. Below is my development environment: * OS: Mac OS X 10.9.2 * Eclipse Kepler * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final) * Java SE 1.7 * Drools Runtime 6.0.1 !https://lh5.googleusercontent.com/-gltHnzUIUg4/U1qbEzVd_LI/AAAAAAAAEYw/mKxE2jv-VVc/w1796-h1168-no/Screen+Shot+2014-04-25+at+10.20.36+AM.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3290) Cannot use a cluster name other than "ejb"

by Chris Stillwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-3290?page=com.atlassian.jira.plugin.... ] Chris Stillwell updated WFLY-3290: ---------------------------------- Attachment: helloworld-test.zip The helloworld-test.zip file contains the source for a simple Stateless session bean, the deployment ear, the standalone.conf, and standalone-ha.xml files I used to test this issue. standalone01-ha.xml adds a remote-outbound-connection named helloworld-connection. The cluster name remains "ejb". standalone02-ha.xml is the same as standalone01-ha.xml, but changes the cluster name to ejb-helloworld. standalone.conf is modified to set the helloworldServer1 variable used in the helloworld outbound-socket-binding in the standalone01 & 02 configs and to override the variables jboss.bind.address.management, jboss.bind.address, and jboss.default.multicast.address. When the ear is deployed using the standalone01-ha.xml configuration the cluster will be formed. However, when using the standalone02-ha.xml configuration the cluster will not be formed. > Cannot use a cluster name other than "ejb" > ------------------------------------------ > > Key: WFLY-3290 > URL: https://issues.jboss.org/browse/WFLY-3290 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Chris Stillwell > Assignee: Paul Ferraro > Priority: Critical > Attachments: helloworld-test.zip > > > When deploying a clustered session bean the cluster will form only if the cluster name is "ejb". If the standalone-ha.xml is modified to use a different cluster name then the cluster will not form. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3290) Cannot use a cluster name other than "ejb"

by Chris Stillwell (JIRA)

Chris Stillwell created WFLY-3290: ------------------------------------- Summary: Cannot use a cluster name other than "ejb" Key: WFLY-3290 URL: https://issues.jboss.org/browse/WFLY-3290 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 8.0.0.Final Reporter: Chris Stillwell Assignee: Paul Ferraro Priority: Critical When deploying a clustered session bean the cluster will form only if the cluster name is "ejb". If the standalone-ha.xml is modified to use a different cluster name then the cluster will not form. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3289) Intermittent failures in PassworkMaskingTestCase

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3289: -------------------------------------- Summary: Intermittent failures in PassworkMaskingTestCase Key: WFLY-3289 URL: https://issues.jboss.org/browse/WFLY-3289 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Test Suite Affects Versions: 8.1.0.CR1 Reporter: Brian Stansberry Assignee: Peter Skopek PasswordMaskingTestCase fails intermittently. See, for example, http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=14404&buildTyp... The log shows this: 05:55:56,496 ERROR [org.jboss.as.arquillian.container.ServerSetupObserver] (main) Setup task failed during setup. Offending class 'org.jboss.as.test.integration.security.passwordmasking.PasswordMaskingTestCase$PasswordMaskingTestCaseSetup@4b584d': java.lang.RuntimeException: Problem creating VaultSession: at org.jboss.as.test.integration.security.common.VaultHandler.<init>(VaultHandler.java:168) at org.jboss.as.test.integration.security.common.VaultHandler.<init>(VaultHandler.java:180) at org.jboss.as.test.integration.security.common.VaultHandler.<init>(VaultHandler.java:188) at org.jboss.as.test.integration.security.passwordmasking.PasswordMaskingTestCase$PasswordMaskingTestCaseSetup.setup(PasswordMaskingTestCase.java:91) at org.jboss.as.arquillian.container.ServerSetupObserver.handleBeforeDeployment(ServerSetupObserver.java:116) at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) . . . at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: java.lang.Exception: Exception encountered: at org.jboss.as.security.vault.VaultSession.initSecurityVault(VaultSession.java:173) at org.jboss.as.security.vault.VaultSession.startVaultSession(VaultSession.java:191) at org.jboss.as.test.integration.security.common.VaultHandler.<init>(VaultHandler.java:166) ... 103 more Caused by: org.jboss.security.vault.SecurityVaultException: javax.crypto.IllegalBlockSizeException: Input length must be multiple of 8 when decrypting with padded cipher at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:210) at org.jboss.as.security.vault.VaultSession.initSecurityVault(VaultSession.java:170) ... 105 more Caused by: javax.crypto.IllegalBlockSizeException: Input length must be multiple of 8 when decrypting with padded cipher at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:750) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676) at com.sun.crypto.provider.PBECipherCore.doFinal(PBECipherCore.java:422) at com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineDoFinal(PBEWithMD5AndDESCipher.java:316) at javax.crypto.Cipher.doFinal(Cipher.java:2087) at org.jboss.security.plugins.PBEUtils.decode(PBEUtils.java:72) at org.jboss.security.plugins.PBEUtils.decode64(PBEUtils.java:81) at org.picketbox.plugins.vault.PicketBoxSecurityVault.decode(PicketBoxSecurityVault.java:362) at org.picketbox.plugins.vault.PicketBoxSecurityVault.loadKeystorePassword(PicketBoxSecurityVault.java:339) at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:204) ... 106 more Per discussion at http://lists.jboss.org/pipermail/wildfly-dev/2014-April/002064.html I am going to @Ignore this test and it is subject to being removed 3 weeks after 8.1.0.Final if not corrected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

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 April 2014