I find myself in that unenviable position of too many moving parts / configurations.
I just ran the example again with the embedded broker and it ran ok. The current configuration in server0/etc works. Comparing... server0/etc/artemis-roles.properties to my installed artemis-roles.properties there is no difference except the obvious differently defined roles. server0/etc/artemis-users.properties to my installed artemis-users.properties there is no difference except the obvious differently defined users. server0/etc/artemis-profile.cmd to my installed artemis-profile.cmd there is no difference except the artemis_home variable. server0/etc/bootstrap.xml to my installed bootstrap .xml there is no difference except my bootstrap has the web app tag. server0/etc/login.config to my installed login.config there is no difference except mine has GuestLoginModule set with admin, admin as user, role. The server0/etc has guest, guest server0/etc/broker.xml to my installed broker.xml there is several differences server0/etc defines three topics, my installed version has deadletter and expiration queues defined. I doubt this affects my problem. my installed version defines under core tag: name, persistence-enabled, journal-type, journal-min-files, journal-pool-files, and journal-buffer-timeout tags. Again, I doubt this affects my problem. server0/etc defines only a single acceptor netty-acceptor, my installed version defines artemis, amqp, stomp, hornet, mqtt. I am very curious why the big differences. server0/etc defines security-settings for the defined topics. My installed version has wild card for any and all. So it remains unclear to me, aside from the first time I ran I had the wrong broker.xml file in play, exactly what is causing my original problem. I think my steps are: copy wholesale the server0/etc files to my installed broker etc folder and run example with -PnoServer if that is ok, then I will add my specific user (admin, user) to the user / roles files and modify the security example code to include a simple test for the new user. If that is ok, then I will try executing my stand-alone example code where I have the problem. if I still do, then there is something wrong with my broker install. Any other ideas? Thanks. From: Justin Bertram-2 [via ActiveMQ] [mailto:ml-node+s2283324n4706170...@n4.nabble.com] Sent: Tuesday, January 19, 2016 12:30 PM To: Pruitt, Byron S Subject: Re: basic security tag in bootstrap.xml Looking at your etc.zip... Your bootstrap.xml looks fine. The jaas-security domain is "activemq" (which is defined in login.config). Your login.config looks fine. It's using the default configuration. However, your artemis-users.properties and artemis-roles.properties don't contain the users/roles that the example expects to be there. That's why you get an authentication failure for the user "bill" when you run the example against your broker (e.g. using 'mvn -PnoServer verify'). Also, your broker.xml doesn't have the security-setting configuration that the example expects so even if you added the right users and roles to the properties files you'd still get failures when running the example against your broker. You can take a look at each of these files from the example (i.e. artemis-users.properties, artemis-roles.properties, and broker.xml) to see what you need to change in your configuration to run the example successfully against your broker. Just to be clear, the output you shared console2.txt is what I would expect from . It looks to me like everything is working properly given the circumstances. Justin ----- Original Message ----- From: "spruitt" <[hidden email]</user/SendEmail.jtp?type=node&node=4706170&i=0>> To: [hidden email]</user/SendEmail.jtp?type=node&node=4706170&i=1> Sent: Tuesday, January 19, 2016 9:38:57 AM Subject: Re: basic security tag in bootstrap.xml yeah. i messed up. Here is the console when not starting broker manually. Also, here are the config files I have been working with on my broker. Hope this makes sense. console2.txt <http://activemq.2283324.n4.nabble.com/file/n4706166/console2.txt> etc.zip <http://activemq.2283324.n4.nabble.com/file/n4706166/etc.zip> -- View this message in context: http://activemq.2283324.n4.nabble.com/basic-security-tag-in-bootstrap-xml-tp4705994p4706166.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. ________________________________ If you reply to this email, your message will be added to the discussion below: http://activemq.2283324.n4.nabble.com/basic-security-tag-in-bootstrap-xml-tp4705994p4706170.html To unsubscribe from basic security tag in bootstrap.xml, click here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4705994&code=c3RldmUucHJ1aXR0QGhwLmNvbXw0NzA1OTk0fDU0MzU1MTgyNg==>. NAML<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> -- View this message in context: http://activemq.2283324.n4.nabble.com/basic-security-tag-in-bootstrap-xml-tp4705994p4706183.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
