[
http://jira.jboss.com/jira/browse/JBMESSAGING-664?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-664:
---------------------------------------------
Fixed. Configuration problem.
The default 4.0.5.GA installer-generated configuration doesn't allow an
unauthenticated user to make JRMP invocations (which is correct). The JRMP invoker is part
of the 'jmx-console' security domain. I've modified the local
'default' 4.0.5.GA jnlp configuration to allow unauthenticated user invocations
and also added 'guest' to the 'admin' role used by 'jmx-console'.
This modification, of course, affects only the testing copy, so it does not introduce any
security risk.
default/conf/login-config.xml:
<application-policy name = "jmx-console">
<authentication>
<login-module
code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag =
"required">
...
<module-option
name="unauthenticatedIdentity">guest</module-option>
</login-module>
</authentication>
</application-policy>
default/conf/props/jmx-console-roles.properties:
admin=JBossAdmin,HttpInvoker,guest
The 4.0.5.GA jnlp installer smoke test fails
--------------------------------------------
Key: JBMESSAGING-664
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-664
Project: JBoss Messaging
Issue Type: Bug
Components: Tests and Performance
Affects Versions: 1.0.1.GA
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Priority: Blocker
Fix For: 1.0.1.SP4
Authentication failure on JMX invocations. Not directly caused by messaging, but must be
fixed nonetheless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira