February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-795) AdvancedLdap login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-795?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-795: -------------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1065513|https://bugzilla.redhat.com/show_bug.cgi?id=1065513] from POST to ASSIGNED > AdvancedLdap login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-795 > URL: https://issues.jboss.org/browse/SECURITY-795 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_2_7 > > Attachments: SECURITY-795.patch > > > AdvancedLdap login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2989) Replacing JSP files through deployment overlays doesn't work for exploded deployments

by Jan Martiska (JIRA)

Jan Martiska created WFLY-2989: ---------------------------------- Summary: Replacing JSP files through deployment overlays doesn't work for exploded deployments Key: WFLY-2989 URL: https://issues.jboss.org/browse/WFLY-2989 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Server Affects Versions: 8.0.0.Final Reporter: Jan Martiska Assignee: Stuart Douglas Attachments: DeploymentOverlayCLITestCase.java I am enhancing DeploymentOverlayCLITestCase with tests for exploded deployments. It seems that with exploded deployments, replacing JSP files doesn't work. Replacing/adding libraries works correctly. Attaching my enhanced version of DeploymentOverlayCLITestCase. It just reuses the old stuff, only deploys deployment0.war and deployment1.war as exploded directories. To reproduce, simply replace the original test with the new source file and run testSimpleOverrideExploded method. It will fail on line 298. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2989) Replacing JSP files through deployment overlays doesn't work for exploded deployments

by Jan Martiska (JIRA)

[ https://issues.jboss.org/browse/WFLY-2989?page=com.atlassian.jira.plugin.... ] Jan Martiska updated WFLY-2989: ------------------------------- Attachment: DeploymentOverlayCLITestCase.java test used as a reproducer > Replacing JSP files through deployment overlays doesn't work for exploded deployments > ------------------------------------------------------------------------------------- > > Key: WFLY-2989 > URL: https://issues.jboss.org/browse/WFLY-2989 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.Final > Reporter: Jan Martiska > Assignee: Stuart Douglas > Attachments: DeploymentOverlayCLITestCase.java > > > I am enhancing DeploymentOverlayCLITestCase with tests for exploded deployments. It seems that with exploded deployments, replacing JSP files doesn't work. Replacing/adding libraries works correctly. > Attaching my enhanced version of DeploymentOverlayCLITestCase. It just reuses the old stuff, only deploys deployment0.war and deployment1.war as exploded directories. To reproduce, simply replace the original test with the new source file and run testSimpleOverrideExploded method. It will fail on line 298. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2988) Class-level @RolesAllowed does not affect inherited methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2988?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2988: ----------------------------------- Fix Version/s: 8.0.1.Final > Class-level @RolesAllowed does not affect inherited methods > ----------------------------------------------------------- > > Key: WFLY-2988 > URL: https://issues.jboss.org/browse/WFLY-2988 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.0.0.Final > Environment: Wildfly 8.0.0.Final running on OpenJDK 1.7.0_45 > Reporter: Daniel Lechner > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > Excerpt from the forum reference: > Basically I have an EJB which derives from a base class. At the EJB itself there is an class-level {{@RolesAllowed}} annotation. With this annotation all methods which are implemented directly in the class can be accessed when the caller has the appropriate role. But when he tries to call a method which has been implemented in the base class, access is denied. > Reading the EJB 3.2 Spec which says > {quote} > Specifying the RolesAllowed or PermitAll or DenyAll annotation on the bean class means that it applies to all applicable business methods of the class. > {quote} > I would suggest that this should work. Although this worked with JBoss AS 5. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2987) RemoteDestinationOutboundSocketBindingService is not stopped when the resource is removed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2987?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2987: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1038465 > RemoteDestinationOutboundSocketBindingService is not stopped when the resource is removed > ----------------------------------------------------------------------------------------- > > Key: WFLY-2987 > URL: https://issues.jboss.org/browse/WFLY-2987 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > > Steps to Reproduce: > 1. add remote-destination-outbound-socket-binding > ./jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" > result is {"outcome" => "success"} > 3. remove remote-destination-outbound-socket-binding > ./bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:remove" > result is {"outcome" => "success"} > 4. add remote-destination-outbound-socket-binding > ./jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" > result is > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: Service jboss.outbound-socket-binding.remote-connection-war-ejb-1 is already registered", > "rolled-back" => true > } > Expected results: > {"outcome" => "success"} > Step 3 should either report reload required or should be fixed -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2988) Class-level @RolesAllowed does not affect inherited methods

by Daniel Lechner (JIRA)

Daniel Lechner created WFLY-2988: ------------------------------------ Summary: Class-level @RolesAllowed does not affect inherited methods Key: WFLY-2988 URL: https://issues.jboss.org/browse/WFLY-2988 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 8.0.0.Final Environment: Wildfly 8.0.0.Final running on OpenJDK 1.7.0_45 Reporter: Daniel Lechner Assignee: Darran Lofthouse Excerpt from the forum reference: Basically I have an EJB which derives from a base class. At the EJB itself there is an class-level {{@RolesAllowed}} annotation. With this annotation all methods which are implemented directly in the class can be accessed when the caller has the appropriate role. But when he tries to call a method which has been implemented in the base class, access is denied. Reading the EJB 3.2 Spec which says {quote} Specifying the RolesAllowed or PermitAll or DenyAll annotation on the bean class means that it applies to all applicable business methods of the class. {quote} I would suggest that this should work. Although this worked with JBoss AS 5. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2987) RemoteDestinationOutboundSocketBindingService is not stopped when the resource is removed

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-2987: --------------------------------- Summary: RemoteDestinationOutboundSocketBindingService is not stopped when the resource is removed Key: WFLY-2987 URL: https://issues.jboss.org/browse/WFLY-2987 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Server Affects Versions: 8.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 8.0.1.Final Steps to Reproduce: 1. add remote-destination-outbound-socket-binding ./jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" result is {"outcome" => "success"} 3. remove remote-destination-outbound-socket-binding ./bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:remove" result is {"outcome" => "success"} 4. add remote-destination-outbound-socket-binding ./jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" result is { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: Service jboss.outbound-socket-binding.remote-connection-war-ejb-1 is already registered", "rolled-back" => true } Expected results: {"outcome" => "success"} Step 3 should either report reload required or should be fixed -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-193) Jboss 5.0.0 GA server getting hanged when trying to hit the application with 50 concurrent user in 1 or 2 mins .

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBVFS-193?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed JBVFS-193. ----------------------------- This is a well known issue in 5.0.0.GA which was fixed in later releases. Please use newer release of AS5. If you do have support contract, then you should rise issue at customer portal http://access.redhat.com/ where can you also download EAP5 releases. > Jboss 5.0.0 GA server getting hanged when trying to hit the application with 50 concurrent user in 1 or 2 mins . > ------------------------------------------------------------------------------------------------------------------ > > Key: JBVFS-193 > URL: https://issues.jboss.org/browse/JBVFS-193 > Project: JBoss VFS > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Reporter: Shnejuti Bose > Assignee: Tomaz Cerar > > I m using Jboss 5.0.0 GA . I was facing issues the temporary jars created in vfs.nested tmp folder. To resolve the this issue , used -Djboss.vfs.forceCopy=false but after this the server is hanged when trying to hit the application with 50 concurrent user in 1 or 2 mins . > Please Help -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2951) Enable alternative provider to be specified for loading key and trust stores.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2951?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2951: ---------------------------------------- Just one comment for attempts to set this up, error message like the following can mean invalid provider configuration at the JVM level - i.e. initialisation failed so the provider was not registered: - {code} 10:31:30,525 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.server.controller.management.security_realm.ManagementRealm.trust-manager: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.ManagementRealm.trust-manager: JBAS015229: Unable to start service at org.jboss.as.domain.management.security.ProviderTrustManagerService.start(ProviderTrustManagerService.java:63) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] Caused by: java.security.KeyStoreException: PKCS11-ServerKeyStore not found at java.security.KeyStore.getInstance(KeyStore.java:616) [rt.jar:1.7.0_45] at org.jboss.as.domain.management.security.ProviderTrustManagerService.start(ProviderTrustManagerService.java:58) ... 5 more Caused by: java.security.NoSuchAlgorithmException: PKCS11-ServerKeyStore KeyStore not available at sun.security.jca.GetInstance.getInstance(GetInstance.java:159) [rt.jar:1.7.0_45] at java.security.Security.getImpl(Security.java:695) [rt.jar:1.7.0_45] at java.security.KeyStore.getInstance(KeyStore.java:613) [rt.jar:1.7.0_45] ... 6 more {code} > Enable alternative provider to be specified for loading key and trust stores. > ----------------------------------------------------------------------------- > > Key: WFLY-2951 > URL: https://issues.jboss.org/browse/WFLY-2951 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > This is to allow pre-defined PKCS#11 providers to be referenced. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-193) Jboss 5.0.0 GA server getting hanged when trying to hit the application with 50 concurrent user in 1 or 2 mins .

by Shnejuti Bose (JIRA)

Shnejuti Bose created JBVFS-193: ----------------------------------- Summary: Jboss 5.0.0 GA server getting hanged when trying to hit the application with 50 concurrent user in 1 or 2 mins . Key: JBVFS-193 URL: https://issues.jboss.org/browse/JBVFS-193 Project: JBoss VFS Issue Type: Support Patch Security Level: Public (Everyone can see) Reporter: Shnejuti Bose Assignee: Tomaz Cerar I m using Jboss 5.0.0 GA . I was facing issues the temporary jars created in vfs.nested tmp folder. To resolve the this issue , used -Djboss.vfs.forceCopy=false but after this the server is hanged when trying to hit the application with 50 concurrent user in 1 or 2 mins . Please Help -- 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, 5 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 February 2014