-
1. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
clebert.suconic Dec 4, 2012 4:24 PM (in response to sudovenko)With all due respect, GIYF, RTM...
http://docs.jboss.org/hornetq/2.2.14.Final/user-manual/en/html/clusters.html#clusters.clusteruser
-
2. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
sudovenko Dec 4, 2012 4:34 PM (in response to clebert.suconic)With all due respect, please read the question: " embedded version of HQ (no config files)" ...
I've seen what you posted prior to posting the question... That does not address my question.
-
3. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
jbertram Dec 4, 2012 4:36 PM (in response to sudovenko)1 of 1 people found this helpfulIf you invoke org.hornetq.core.config.Configuration#setClusterPassword with something other than "CHANGE ME!!" does that not eliminate the WARN?
-
4. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
sudovenko Dec 4, 2012 4:43 PM (in response to jbertram)Is there any way to do it through the API?
-
5. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
jbertram Dec 4, 2012 4:47 PM (in response to sudovenko)I assume you are creating a org.hornetq.core.server.embedded.EmbeddedHornetQ and subsequently invoking org.hornetq.core.server.embedded.EmbeddedHornetQ#setConfiguration. Is that correct? If so, then you can invoke org.hornetq.core.config.Configuration#setClusterPassword on the org.hornetq.core.config.Configuration which you pass.
-
6. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
clebert.suconic Dec 4, 2012 4:49 PM (in response to sudovenko)1 of 1 people found this helpfulThat's the same thing... the cluster-password on the XML is translated as the property clusterPassword on the class Configuration
just call configuration.setClusterPassword before you start the server.
-
7. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
clebert.suconic Dec 4, 2012 4:51 PM (in response to sudovenko)I'm sorry on that case. We get some weird questions from time to time and I thought you didn't even look at the sources before posting it.
Your question is more how the configuration is translated into the API. ConfigurationImpl (or configuration) has always (or almost aways) a contrapart on the XML. Translating stuff between XML and Configuration should be a simple matter. Take a look on that.
-
8. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
sudovenko Dec 4, 2012 5:44 PM (in response to jbertram)Thank you champs!
Got it sorted out with your help.
Just as a note, it would beneficial to see Configuration class in the API.
Thanks to all of you!
-
9. Re: WARNING: Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default.
clebert.suconic Dec 4, 2012 6:18 PM (in response to sudovenko)I'm not sure what happened but I had post a complete example for you, and it got lost...
But I'm glad you figured out
the example I posted (but for some reason didn't commit on my add-reply, maybe I missed something.. dunno) was based on the embedded example...
Good you figured out