November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-661) CertRolesLoginModule does not substitute variables in paths to property files

by Martin Gencur (JIRA)

Martin Gencur created SECURITY-661: -------------------------------------- Summary: CertRolesLoginModule does not substitute variables in paths to property files Key: SECURITY-661 URL: https://issues.jboss.org/browse/SECURITY-661 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v4_0_9.Final Reporter: Martin Gencur Assignee: Anil Saldhana Fix For: PicketBox_4_0_10.Final When I use CertificateRoles module in AS7 configuration and specify a path to roles.properties like this: <module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/> ,the server throws the following error: {code} ERROR [org.jboss.security.auth.spi.CertRolesLoginModule] (http-/127.0.0.1:8443-1) Failed to load users/passwords/role files: java.io.IOException: No properties file: ${jboss.server.config.dir}/roles.properties or defaults: defaultRoles.properties found at org.jboss.security.auth.spi.Util.loadProperties(Util.java:228) [picketbox-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.auth.spi.CertRolesLoginModule.loadRoles(CertRolesLoginModule.java:153) [picketbox-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.auth.spi.CertRolesLoginModule.initialize(CertRolesLoginModule.java:108) [picketbox-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [rt.jar:1.6.0_26] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [rt.jar:1.6.0_26] at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [rt.jar:1.6.0_26] at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:449) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:383) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:371) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:160) [picketbox-infinispan-4.0.9.Final-redhat-1.jar:4.0.9.Final-redhat-1] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:287) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.apache.catalina.authenticator.SSLAuthenticator.authenticate(SSLAuthenticator.java:135) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:455) [jbossweb-7.0.16.Final-redhat-1.jar:] at com.jboss.datagrid.endpoint.RestSecurityContext.invoke(RestSecurityContext.java:143) [jboss-datagrid-server-integration-6.0.0.ER11-redhat-1.jar:6.0.0.ER11-redhat-1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] {code} However, when I put the absolute path to that file, it is found. This is noticeable difference from UsersRoles module where it works as expected. The problem is in class picketbox/security-jboss-sx/jbosssx/src/main/java/org/jboss/security/auth/spi/CertRolesLoginModule.java -- 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

11 years, 10 months

2
7
0 / 0

[JBoss JIRA] (AS7-6011) After redeploy an application to a domain the old content is not removed at slave host

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-6011: ------------------------------------- Summary: After redeploy an application to a domain the old content is not removed at slave host Key: AS7-6011 URL: https://issues.jboss.org/browse/AS7-6011 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.2.0.Alpha1 Environment: OS Fedora17 Two instances in domain mode. DC without server HC with one server Reporter: Wolf-Dieter Fink Assignee: Brian Stansberry If an application deployed on a domain slave HC the content is not removed if a new version of the application is deployed with 'deploy xxx --force' The logfile looks correct and shows: JBAS018565: Replaced deployment "appone.ear" with deployment "appone.ear" JBAS014901: Content removed from location /.../domain/servers/server-one/data/content/5e/c06cd5b58b1b6578188d822b351a14f974804c/content If the folder is checked the file still exists. An undeploy remove the files correct with the same log messages. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5899) UCS-2 CodeSet Interop Issue

by Nick Cross (JIRA)

[ https://issues.jboss.org/browse/AS7-5899?page=com.atlassian.jira.plugin.s... ] Nick Cross reassigned AS7-5899: ------------------------------- Assignee: Brad Maxwell (was: Nick Cross) > UCS-2 CodeSet Interop Issue > --------------------------- > > Key: AS7-5899 > URL: https://issues.jboss.org/browse/AS7-5899 > Project: Application Server 7 > Issue Type: Bug > Components: IIOP > Affects Versions: 7.1.2.Final (EAP) > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Labels: jacorb > Fix For: Open To Community > > > Interoperability issue when client in JBoss EAP 6 calls IBM WebSphere. The client in JBoss EAP 6 sends "foo" but the server side IBM WebSphere receives "?foo" -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-6004) Inconsistent tab completion behaviour between commands and arguments

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-6004: -------------------------------- Summary: Inconsistent tab completion behaviour between commands and arguments Key: AS7-6004 URL: https://issues.jboss.org/browse/AS7-6004 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Jeff Mesnil Assignee: Alexey Loubyansky Priority: Minor When tab is used for completion, the behavior changes when there is only 1 remaining candidate. For commands, when the completion leads to a single candidate, a whitespace is appended and we can proceed to the arguments For arguments using a TabCompleter, when the completion leads to a single candidate, no whitespace is appended and we have to type it to be able to proceed to the next argument Example: * deployment-over<TAB> => will complete to deployment-overlay<WHITESPACE><CURSOR> (a whitespace is appended to the single candidate) * deployment-overlay a<TAB> => will complete to deployment-over add<CURSOR> (no whitespace appended even though add is the only candidate matched) -- 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

11 years, 10 months

2
4
0 / 0

[JBoss JIRA] (AS7-6007) Logging 1.1 parsing is broken

by Kabir Khan (JIRA)

Kabir Khan created AS7-6007: ------------------------------- Summary: Logging 1.1 parsing is broken Key: AS7-6007 URL: https://issues.jboss.org/browse/AS7-6007 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: Kabir Khan Assignee: Josef Cacek Fix For: 7.2.0.Alpha1 Trying to debug an issue in logging transformers when old slaves connect to master's DC, I noticed that SubsystemParsing11Test was not getting run. It's name needs to be changed to SubsystemParsing11TestCase to be included in the run. Doing that I noticed that 1.1 parsing is broken, and the same probably goes for 1.0 parsing. 1.0 parsing also needs its own test. -- 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

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (AS7-5595) Support custom transaction isolation levels

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-5595: ------------------------------------ Summary: Support custom transaction isolation levels Key: AS7-5595 URL: https://issues.jboss.org/browse/AS7-5595 Project: Application Server 7 Issue Type: Task Components: JCA Affects Versions: 7.1.3.Final (EAP) Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) -- 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

11 years, 10 months

2
1
0 / 0

[JBoss JIRA] (AS7-5951) Cannot reliably deploy OSGi host and fragment bundles using the deployments folder

by Paul Illingworth (JIRA)

Paul Illingworth created AS7-5951: ------------------------------------- Summary: Cannot reliably deploy OSGi host and fragment bundles using the deployments folder Key: AS7-5951 URL: https://issues.jboss.org/browse/AS7-5951 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.2.0.Alpha1 Environment: Windows XP SP3 Reporter: Paul Illingworth Assignee: Thomas Diesler If I deploy guice-3.0.0 (host bundle), guice-servlet (fragment) and guice-persist (fragment) into the "deployments" folder then the there is no guarantee the fragments will be installed before the host and so they may not be attached to the host when it resolves. This happens on starting the application server. Sometimes the fragments are attached, sometimes they aren't. If I install the bundles into the "bundles" folder structure and add capability entries to the standalone.xml file then it works as expected. I am using 7.2.0-Alpha1 built from cb72a7cd1669131b28a552f1dbf3c2582ad19813. -- 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

11 years, 10 months

2
13
0 / 0

[JBoss JIRA] (JBRULES-3691) Property Reactive: using nested accessor in modify() seems to prevent the correct re-evaluation of the rules.

by Esteban Aliverti (JIRA)

Esteban Aliverti created JBRULES-3691: ----------------------------------------- Summary: Property Reactive: using nested accessor in modify() seems to prevent the correct re-evaluation of the rules. Key: JBRULES-3691 URL: https://issues.jboss.org/browse/JBRULES-3691 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 6.0.0.Alpha1 Reporter: Esteban Aliverti Assignee: Mario Fusco The usage of nested accessors in modify() seems to prevent rules to be re-evaluated, or the re-evaluation result is not the expected one. -- 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

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (AS7-5994) Infinispan cache container not displayed

by Heiko Braun (JIRA)

Heiko Braun created AS7-5994: -------------------------------- Summary: Infinispan cache container not displayed Key: AS7-5994 URL: https://issues.jboss.org/browse/AS7-5994 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- 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

11 years, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-3524) HostControllerConnectionService connection timeout is not configurable

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3524: ------------------------------------- Summary: HostControllerConnectionService connection timeout is not configurable Key: AS7-3524 URL: https://issues.jboss.org/browse/AS7-3524 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Jason Greene I am seeing intermittent failures when starting AS7 in domain mode. It seems that this is due to HostControllerConnectionService has hardcoded 15s timeout when trying to connect to DC. I think that this value should be configurable. HostControllerConnectionService.java: ... ProtocolChannelClient.Configuration configuration = new ProtocolChannelClient.Configuration(); configuration.setEndpoint(endpointInjector.getValue()); configuration.setConnectionTimeout(15000); configuration.setUri(new URI("remote://" + hcAddressInjector.getValue().getHostName() + ":" + hcAddressInjector.getValue().getPort())); client = ProtocolChannelClient.create(configuration); ... Exception I am getting: [Server:server-two] 13:52:54,766 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:103) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] -- 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

11 years, 10 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012