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. Tim On Tue, Apr 7, 2015 at 1:41 PM, Scammell <mark.har...@meridianenergy.co.nz> wrote: > Tim Bain wrote > > Those are IDs (and I'm positive they have to be unique); I was referring > > to > > <property name="name" value="BASIC" /> > > in each bean. Maybe Spring doesn't > > mind that, I don't remember (I mainly use annotations these days), but it > > seemed like an easy thing for you to check. > > > > More generally, I'd simplify your config till it works and then you can > > add > > back in the bells and whistles. So any references to admin are > > superfluous > > to what you're currently trying to get working; comment all that out and > > see if it works. If it does, you know something's wrong with that aspect > > of your config; if not, at least you know that's not the problem. > > Well, the configuration supplied in jetty.xml is the default one included > in > the download, so I'm not sure what I can simplify. I've followed the > instructions on the ActiveMQ website > (http://activemq.apache.org/web-console.html) and I'm still getting the > error. > > Mark > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/SecurityException-User-is-not-authenticated-tp4694392p4694457.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
