[JBoss JIRA] (AS7-5269) HornetQ interceptors are not supported
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5269?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-5269:
---------------------------------------
The configuration for these should support a module attribute so they can be loaded without requiring a modification to the HQ subsystem module's module.xml.
> HornetQ interceptors are not supported
> --------------------------------------
>
> Key: AS7-5269
> URL: https://issues.jboss.org/browse/AS7-5269
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> HornetQ interceptors are not supported by the messaging subsystem.
> Their attributes are handled by the XML parser but they are not set when adding the HornetQ server instance.
> Moreover, passing the interceptor class name is not enough. Since they are loaded by HornetQ, its classloader must be able to access them. The interceptors must be put in a JBoss module that is declared as a transitive dependency of org.hornetq module.
--
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, 9 months
[JBoss JIRA] (SECURITY-703) Picketbox logs an ERROR on each failed login
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-703?page=com.atlassian.jira.plug... ]
Stefan Guilhen closed SECURITY-703.
-----------------------------------
Fix Version/s: PIcketBox_4_0_15.Final
Resolution: Done
I've changed the log level of failed login attempts to DEBUG to avoid polluting the AS logs with error messages. Users can still investigate failed logins by adding a org.jboss.security category with level = DEBUG.
> Picketbox logs an ERROR on each failed login
> --------------------------------------------
>
> Key: SECURITY-703
> URL: https://issues.jboss.org/browse/SECURITY-703
> Project: PicketBox
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Thomas Heute
> Assignee: Stefan Guilhen
> Priority: Critical
> Fix For: PIcketBox_4_0_15.Final
>
>
> Picketbox logs an ERROR with a stacktrace on each failed login:
> See:
> catch (LoginException e)
> {
> // Don't log anonymous user failures unless trace level logging is on
> if (principal != null && principal.getName() != null)
> PicketBoxLogger.LOGGER.errorDuringLogin(e);
> authException = e;
> }
> 09:57:30,100 ERROR [org.jboss.security] (http-/127.0.0.1:8080-6) PBOX000206: Login failure: javax.security.auth.login.LoginException: Login failed for
> at org.exoplatform.services.security.jaas.DefaultLoginModule.login(DefaultLoginModule.java:136) [exo.core.component.security.core-2.5.0-CR1.jar:2.5.0-CR1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) [rt.jar:1.6.0_25]
> at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [rt.jar:1.6.0_25]
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [rt.jar:1.6.0_25]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_25]
> at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [rt.jar:1.6.0_25]
> at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [rt.jar:1.6.0_25]
> at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:408) [picketbox-infinispan-4.0.13.Final-redhat-1.jar:4.0.13.Final-redhat-1]
> in http://anonsvn.jboss.org/repos/picketbox/tags/4.0.14.Final/picketbox-infi...
> Failed login are expected from users and shouldn't be logged. This will seriously pollute EPP 6 logs.
--
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, 9 months
[JBoss JIRA] (SECURITY-665) Incorrect warning about invalid option passwordIsA1Hash in login modules
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/SECURITY-665?page=com.atlassian.jira.plug... ]
Stefan Guilhen closed SECURITY-665.
-----------------------------------
Fix Version/s: PIcketBox_4_0_15.Final
Resolution: Done
The passwordIsA1Hash option has been added to the set of valid options in UsernamePasswordLoginModule.
> Incorrect warning about invalid option passwordIsA1Hash in login modules
> ------------------------------------------------------------------------
>
> Key: SECURITY-665
> URL: https://issues.jboss.org/browse/SECURITY-665
> Project: PicketBox
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: PicketBox_v4_0_9.Final
> Reporter: Martin Gencur
> Assignee: Stefan Guilhen
> Fix For: PIcketBox_4_0_15.Final
>
>
> As I described in in my last post in https://community.jboss.org/message/744521#744521, I had a problem with DIGEST authentication and passwordIsA1Hash option configured in JBossAS 7.
> IMO one of the following classes should enlist passwordIsA1Hash option among their valid options: AbstractServerLoginModule, UsernamePasswordLoginModule, UsersRolesLoginModule. Now it's missing and login modules scream that the option is invalid (in my case UsersRolesLoginModule).
--
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, 9 months
[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ]
Kabir Khan commented on AS7-6202:
---------------------------------
Probably the slave interprets whatever is coming from the DC as meaning activation='eager' rather than 'lazy'
> Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
> ---------------------------------------------------------------
>
> Key: AS7-6202
> URL: https://issues.jboss.org/browse/AS7-6202
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Kabir Khan
> Assignee: Thomas Diesler
> Attachments: domain.xml, host.xml
>
>
> I noticed this when working on the mixed-domain tests. The attached domain.xml and host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers auto-start="false".
> To reproduce, start up a DC built from master using those files. Then start up a slave HC built from 7.1.2.Final or 7.1.3.Final using a command like:
> ./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999
> Now in CLI:
> {code}
> [domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" => "file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}]
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@localhost:9999 /] /deployment=test.war:remove [domain@localhost:9999 /] /server-group=main-server-group/deployment=test.war:add(enabled=true)
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"kabirs-macbook-pro.local" => {"server-one" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]},
> "rolled-back" => true
> }}}}}}
> }
> {code}
> The console log for the slave shows
> {code}
> [Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war"
> [Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /test
> [Server:server-one] 17:21:22,771 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]}
> [Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 42ms
> {code}
> The deployment is very simple, and just contains an html file:
> {code}
> $unzip -l testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
> Archive: testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
> Length Date Time Name
> -------- ---- ---- ----
> 210 12-17-12 16:34 index.html
> -------- -------
> 210 1 file
> {code}
--
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, 9 months
[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ]
Kabir Khan commented on AS7-6202:
---------------------------------
NAKACK2 will also need changing to NAKACK for jgroups. Removing the osgi subsystem from the DC's domain.xml, the deployment works as expected.
> Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
> ---------------------------------------------------------------
>
> Key: AS7-6202
> URL: https://issues.jboss.org/browse/AS7-6202
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Kabir Khan
> Assignee: Thomas Diesler
> Attachments: domain.xml, host.xml
>
>
> I noticed this when working on the mixed-domain tests. The attached domain.xml and host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers auto-start="false".
> To reproduce, start up a DC built from master using those files. Then start up a slave HC built from 7.1.2.Final or 7.1.3.Final using a command like:
> ./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999
> Now in CLI:
> {code}
> [domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" => "file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}]
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@localhost:9999 /] /deployment=test.war:remove [domain@localhost:9999 /] /server-group=main-server-group/deployment=test.war:add(enabled=true)
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"kabirs-macbook-pro.local" => {"server-one" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]},
> "rolled-back" => true
> }}}}}}
> }
> {code}
> The console log for the slave shows
> {code}
> [Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war"
> [Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /test
> [Server:server-one] 17:21:22,771 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]}
> [Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 42ms
> {code}
> The deployment is very simple, and just contains an html file:
> {code}
> $unzip -l testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
> Archive: testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
> Length Date Time Name
> -------- ---- ---- ----
> 210 12-17-12 16:34 index.html
> -------- -------
> 210 1 file
> {code}
--
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, 9 months
[JBoss JIRA] (AS7-6202) Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-6202?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated AS7-6202:
----------------------------
Description:
I noticed this when working on the mixed-domain tests. The attached domain.xml and host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers auto-start="false".
To reproduce, start up a DC built from master using those files. Then start up a slave HC built from 7.1.2.Final or 7.1.3.Final using a command like:
./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999
Now in CLI:
{code}
[domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" => "file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}]
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
[domain@localhost:9999 /] /deployment=test.war:remove [domain@localhost:9999 /] /server-group=main-server-group/deployment=test.war:add(enabled=true)
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" => true,
"server-groups" => {"main-server-group" => {"host" => {"kabirs-macbook-pro.local" => {"server-one" => {"response" => {
"outcome" => "failed",
"result" => undefined,
"failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]},
"rolled-back" => true
}}}}}}
}
{code}
The console log for the slave shows
{code}
[Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war"
[Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /test
[Server:server-one] 17:21:22,771 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]}
[Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 42ms
{code}
The deployment is very simple, and just contains an html file:
{code}
$unzip -l testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
Archive: testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
Length Date Time Name
-------- ---- ---- ----
210 12-17-12 16:34 index.html
-------- -------
210 1 file
{code}
> Deploying to a 7.2 DC with a 7.1.2 or 7.1.3 slave fails in OSGi
> ---------------------------------------------------------------
>
> Key: AS7-6202
> URL: https://issues.jboss.org/browse/AS7-6202
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Kabir Khan
> Assignee: Thomas Diesler
> Attachments: domain.xml, host.xml
>
>
> I noticed this when working on the mixed-domain tests. The attached domain.xml and host.xml contain adjustments for the older slave to work (replacing the MERGE3 jgroups protocol with MERGE2, since 7.1.x does not have that version), and makes all its servers auto-start="false".
> To reproduce, start up a DC built from master using those files. Then start up a slave HC built from 7.1.2.Final or 7.1.3.Final using a command like:
> ./build/target/jboss-as-7.1.3.Final/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999
> Now in CLI:
> {code}
> [domain@localhost:9999 /] /deployment=test.war:add(content=[{"url" => "file:/Users/kabir/sourcecontrol/jboss-as7/git/jboss-as/testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war"}]
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@localhost:9999 /] /deployment=test.war:remove [domain@localhost:9999 /] /server-group=main-server-group/deployment=test.war:add(enabled=true)
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"kabirs-macbook-pro.local" => {"server-one" => {"response" => {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]},
> "rolled-back" => true
> }}}}}}
> }
> {code}
> The console log for the slave shows
> {code}
> [Server:server-one] 17:21:22,201 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war"
> [Server:server-one] 17:21:22,556 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /test
> [Server:server-one] 17:21:22,771 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.osgi.as.module.registration.\"deployment.test.war:main\" Missing[jbosgi.Environment]"]}
> [Server:server-one] 17:21:22,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test.war in 42ms
> {code}
> The deployment is very simple, and just contains an html file:
> {code}
> $unzip -l testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
> Archive: testsuite/mixed-domain/target/deployments/MixedDomainDeployment_7_1_2_Final_TestCase/archives/test.war
> Length Date Time Name
> -------- ---- ---- ----
> 210 12-17-12 16:34 index.html
> -------- -------
> 210 1 file
> {code}
--
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, 9 months