> I just wanted to make sure I didn't do something wrong from a security point of view.
I can't say whether or not you've done something wrong from a security point of view. It's plausible that those applications *should* be able to connect successfully with their current credentials, but it's equally plausible that they are being appropriately denied. All I can say is that the WARN message looks "normal." Do you have any reason to believe one way or the other? > In particular, I'm trying to understand why certain 172.x.x.x addresses keep causing the warnings. Presumably there are messaging applications on those hosts connecting to your broker with the incorrect credentials. I suppose you'll have to do some legwork to see exactly what those applications are and why they're using the wrong credentials (if they are, in fact, using the wrong credentials). Justin On Wed, Nov 30, 2022 at 3:46 PM Steve Hiller <steve.hil...@randstadusa.com> wrote: > Hi Justin, > > Thanks for the quick reply! I just wanted to make sure I didn't do > something wrong from a security point of view. > In particular, I'm trying to understand why certain 172.x.x.x > addresses keep causing the warnings. > > Steve > > On Wed, Nov 30, 2022 at 4:14 PM Justin Bertram <jbert...@apache.org> > wrote: > > > > This looks like a normal WARN message about a connection attempt from an > > unauthenticated user. It's not a problem, per se. You can adjust the > > logging to omit it if you want. > > > > Do you have reason to believe this WARN message is not legitimate? > > > > > > Justin > > > > On Wed, Nov 30, 2022 at 3:07 PM Steve Hiller < > steve.hil...@randstadusa.com> > > wrote: > > > > > Hi All, > > > > > > I am going the following warning in the logs for my > > > kubernetes-deployed Artemis instance: > > > > > > 2022-11-30 20:18:10,015 WARN > > > [org.apache.activemq.artemis.core.server] AMQ222216: Security problem > > > while authenticating: AMQ229031: Unable to validate user from > > > /172.28.2.78:57456. Username: artemis; SSL certificate subject DN: > > > unavailable > > > > > > This message is produced for a variety of IP addresses and ports but > > > all for username artemis. I've done some googling but didn't see any > > > clear advice. My setup is as follows: > > > > > > Single Artemis instance, deployed to a Google kubernetes cluster, > > > using the Docker image based on the > > > apache-artemis-2.26.0-Source/artemis-docker sample. > > > > > > Any advice on this issue would be greatly appreciated! > > > > > > Thanks, > > > > > > Steve Hiller > > > > > > -- > > > This email message is for the sole use of the intended recipient(s) and > > > may > > > contain confidential and privileged information. Any unauthorized > review, > > > use, disclosure or distribution is prohibited. If you are not the > intended > > > recipient, please contact the sender by reply email and destroy all > copies > > > of the original message. > > > > > > > > > > -- > Steve Hiller > Manager, Software Development (Engagement) > > Randstad > 6750 North Andrews Avenue > Ft. Lauderdale, FL 33309 > 954.308.8230 (o) > 954.483.8452 (m) > steve.hil...@randstadusa.com > www.randstad.com > > This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact the sender by > reply email and destroy all copies of the original message. > > -- > This email message is for the sole use of the intended recipient(s) and > may > contain confidential and privileged information. Any unauthorized review, > use, disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. > >
