Tim Bain wrote > My jetty.xml file has only your second bean, not the first one (and our > users list in jetty-realm.properties includes only admin users), and > authentication works, so commenting out your entire securityConstraint > bean > seems like an easy way to simplify your config and see if authentication > works in that simpler configuration. > > If that works, then you can dig into why adding your second bean fails. > I'd start by validating your assumption that you're supposed to be able to > have more than one securityConstraint in the first place; the instructions > on the web site reference uncommenting **a** security constraint config > (not multiple of them), so I'd make sure that what you're assuming to be > legal really is.
I have found that the jetty.xml file is OK; the issue was more to do with the authentication plugin that I specified in activemq.xml. I'll create a new thread for this. Thanks, Mark -- View this message in context: http://activemq.2283324.n4.nabble.com/SecurityException-User-is-not-authenticated-tp4694392p4694481.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
