MQTT Username and password

[trsimmons7]

For email, we embed the full certificate chain. For HTTPS and MQTTS we are essentially skipping the server certificate validation for now. Not sure how Mosquitto feels about self-signing. There are public free CAs out there though.

Well.... no progress on this -

I've tried two brokers and two clients. Any combination of no username/no password, username/password, TLS or no TLS works for the two broker configurations and two clients.

BUT the BRX doesn't work for anything other than no username/ no password.

I need to solve this problem. The error logs aren't helping me.

The attachments are for username/password only.

I'm digging through some wireshark logs now to find a clue......

[BobO]

I just set up mosquitto to use a password file. Entered one username/password combination with mosquitto_passwd.exe and changed the mosquitto.conf to point to my file. It works fine for me. I do get the "Socket error on client <unknown>, disconnecting." when the user name or password is incorrect.

Is your password really long? I think the released code is limited to 19 characters. We have new stuff coming that greatly increases that.

[trsimmons7]

I just set up mosquitto to use a password file. Entered one username/password combination with mosquitto_passwd.exe and changed the mosquitto.conf to point to my file. It works fine for me. I do get the "Socket error on client <unknown>, disconnecting." when the user name or password is incorrect.

Is your password really long? I think the released code is limited to 19 characters. We have new stuff coming that greatly increases that.

Nope - just 9 characters!
Yeah - i can use Mqtt Explorer or mqttbox as a client with username and password and it connects. I just can't see the problem.

[BobO]

Use Wireshark. Set the filter to tcp.port == 1883 to make it easier to find what you need. Isolate the MQTT Connect Command packet. The last bytes of the packet are the user name and password. Make sure that matches what you think they should be. I'm happy to look at the packet if you'd like.

[trsimmons7]

Use Wireshark. Set the filter to tcp.port == 1883 to make it easier to find what you need. Isolate the MQTT Connect Command packet. The last bytes of the packet are the user name and password. Make sure that matches what you think they should be. I'm happy to look at the packet if you'd like.

Well there's your problem! Hell i don't know.....    

I attached a wireshark screen shot - one shows the correct username/password but the username and password flags are not set. This does not work.
I cleared the PLC memory - reloaded the program and it worked. See the other screenshot - correct username and password but the username and password flags are set.

I can't explain it. And I can break it again - trying to decide exactly how - not sure if its checking the tls box or the Enable Account box or a combination that does it.

[BobO]

That certainly doesn't sound right. Should be an easy bug to fix though.

[BobO]

Looks like if the will is turned on, it loses the password and user name flags. Easy fix.

[trsimmons7]

Looks like if the will is turned on, it loses the password and user name flags. Easy fix.

I thought i was going crazy.
I'll keep an eye out for the update.

thanks
t.

[BobO]

I thought i was going crazy.
I'll keep an eye out for the update.

Well...in fairness...this doesn't prove that you aren't. 

Thanks for your help (and patience) on this. I owe you a beverage of your choice or some Host swag.

Update should be out next week.

[trsimmons7]

I thought i was going crazy.
I'll keep an eye out for the update.

Well...in fairness...this doesn't prove that you aren't. 

Thanks for your help (and patience) on this. I owe you a beverage of your choice or some Host swag.

Update should be out next week.

Excellent!
Enjoy your weekend. - I'm fixing my beverage now......

thanks
t.