[
http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1111:
--------------------------------------
Nothings stops the server running, they just get the warning since there's a potential
security risk until they specify a password.
It's a bit like installing Oracle and not changing the default password (if there is
one - I can't remember?) - you get the idea.
We could take a "head in the sand" approach and not log a warning but I
don't think this is a good idea - is this what you are suggesting?
BTW the text was changed some days ago.
JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server
log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED
FROM THE INSTALLATION DEFAULT
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1111
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1111
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Security
Affects Versions: 1.4.0.GA
Environment: RHEL5
Java 1.5
JBESB - At revision 15800
JBM 1.4.0.GA
Reporter: Len DiMaggio
Assigned To: Tim Fox
Priority: Minor
Fix For: Unscheduled
This is coming from:
jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE
CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
I noticed this with ESB - from svn revision 15800 on oct 12 -
http://jira.jboss.com/jira/browse/JBESB-1172
--
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