search

Raynerv / node-red-contrib-mqttssl

A node-red node for MQTT over SSL/TLS
4 stars 6 forks source link

Authentication fails #1

Closed tedstriker closed 9 years ago

tedstriker commented 9 years ago

Hi there,

I'm experiencing trouble connecting to the broker using name + password for authentication. The credentials are alright, as I use them with other clients as well. Different ones (also working with other clients) don't work either. I tried that just to rule out possible ACL issues. The broker I use is mosquitto 1.3.4 and Node-RED 0.10.4

Weird thing is: when I allow anonymous users the connection is established immediately.

Do you have a hint, where to look at to fix it? Also username and password are not loaded, when I reconfigure the broker config node.

Any help is appreciated. Thank you.

best regards, Ted

adrianbro commented 9 years ago

I am having the same issue using latest version of node-red and apollo broker

dmelpi commented 9 years ago

same here with Node Red 0.10.6 and mosquitto 1.4.1

Raynerv commented 9 years ago

I'm guessing this has something to do with how the config is handled, perhaps due to changes in node-red. I might have a solution later this week

tedstriker commented 9 years ago

Hi Raynerv, could you figure out what the problem is already? If not, is there a way I/we can assist you?

VirTERM commented 9 years ago

I have similar problem, is this not related to SSL vs TLS?

tedstriker commented 9 years ago

The initially described error doesn't have anything to do with TLS vs. SSL - also the referenced pull request fixed it. I already got it up and running.

Raynerv commented 9 years ago

@tedstriker Thanks alot for looking into this. I've merged your changes and released 0.0.5 to npm. I currently don't have a SSL-enabled broker to test this release on. Can you confirm that this release works, before I close this issue?

tedstriker commented 9 years ago

@raynerv you're welcome. I already use it with NodeRED 0.10.6 and mosquito 1.4.2 TLS enabled. A positive response from a second person would be great. A restart of node.js and a reinsertion of the mqttssl node might be necessary.

VirTERM commented 9 years ago

Actually, it does not work for me. It authenticates but than gets disconnected right away (user name/pass based authentication). Mosquitto 1.4.2 and NodeRed 0.10.6 Other mqtt clients from iOS, command line and Macos (mqtt.fx) connect without any problem

Wojtek

On Jun 3, 2015, at 3:13 AM, tedstriker notifications@github.com wrote:

@raynerv https://github.com/raynerv you're welcome. I already use it with NodeRED 0.10.6 and mosquito 1.4.2 TLS enabled. A positive response from a second person would be great. A restart of node.js and a reinsertion of the mqttssl node might be necessary.

— Reply to this email directly or view it on GitHub https://github.com/Raynerv/node-red-contrib-mqttssl/issues/1#issuecomment-108223816.

tedstriker commented 9 years ago

So authentication works fine so far, but you get kicked out afterwards? The only thing that got changed is the way credentials are being saved in node red. When it comes to authorization / certificate validation etc. I haven't changed a thing. You might try test.mosquitto

tedstriker commented 9 years ago

So authentication works fine so far, but you get kicked out afterwards? The only thing that got changed is the way credentials are being saved in node red. When it comes to authorization / certificate validation etc. I haven't changed a thing. You might try test.mosquitto

tedstriker commented 9 years ago

Sorry. I hit close by accident. You might try test.mosquitto.org to narrow it down

VirTERM commented 9 years ago

I need to run more tests, but your authentication seems to be working as I can see in mosquito logs if I specify incorrect password. I still can not connect, despite ANY other client can connect….

The message is now very verbose, basically: Socket error on client node-red-ssl11, disconnecting.

On Jun 3, 2015, at 11:48 AM, tedstriker notifications@github.com wrote:

So authentication works fine so far, but you get kicked out afterwards? The only thing that got changed is the way credentials are being saved in node red. When it comes to authorization / certificate validation etc. I haven't changed a thing. You might try test.mosquitto

— Reply to this email directly or view it on GitHub https://github.com/Raynerv/node-red-contrib-mqttssl/issues/1#issuecomment-108493200.

tedstriker commented 9 years ago

I wish you good luck finding a solution - as far as I can tell, this issue seems fixed. If necessary, you can open another issue.