Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MsgFlo participants on coordinator unable to subscribe due to permissions #1

Closed
jonnor opened this issue Oct 7, 2016 · 1 comment
Closed
Labels

Comments

@jonnor
Copy link
Contributor

jonnor commented 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

@jonnor jonnor added the bug label Oct 7, 2016
@jonnor jonnor changed the title MsgFlo participants on coordinator unable to subscribe MsgFlo participants on coordinator unable to subscribe due to permissions Oct 7, 2016
@jonnor
Copy link
Contributor Author

jonnor commented Oct 8, 2016

Wrote tests for our access lists, in https://github.com/bitraf/bitraf-iot/blob/master/test/access.coffee
and then found that allowing readwrite + in mosquitto did not break the stricter permissions on /bitraf/door/+/open. CC @trygvis

@jonnor jonnor closed this as completed Oct 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant