You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because they attempt to subscribe to topics on form myparticipant.PORT, which is currently not allowed to read/write from in our mosquitto config. In general only /public/* is open for R/W...
So either all participants must obey a prefix (msgflo/msgflo-nodejs#11 and same in msgflo-python, etc), or we change this configuration to make most things open. This should be fine as long as we ensure that our security sensitive topics. A test-suite that ensures this would be probably be the best anyways.
While debugging found that there are no error for subscription failures: msgflo/msgflo-nodejs#10
The text was updated successfully, but these errors were encountered:
jonnor
changed the title
MsgFlo participants on coordinator unable to subscribe
MsgFlo participants on coordinator unable to subscribe due to permissions
Oct 7, 2016
Because they attempt to subscribe to topics on form
myparticipant.PORT
, which is currently not allowed to read/write from in our mosquitto config. In general only/public/*
is open for R/W...So either all participants must obey a prefix (msgflo/msgflo-nodejs#11 and same in msgflo-python, etc), or we change this configuration to make most things open. This should be fine as long as we ensure that our security sensitive topics. A test-suite that ensures this would be probably be the best anyways.
While debugging found that there are no error for subscription failures:
msgflo/msgflo-nodejs#10
The text was updated successfully, but these errors were encountered: