Support multiple access levels for runtimes #278

Closed
jonnor opened this Issue May 31, 2014 · 0 comments

Projects

None yet

2 participants

@jonnor
Member
jonnor commented May 31, 2014

To allow people to use runtimes around them, we want to support multiple levels of access for non-authorized users. In escalating order of privilege:

  • Read exported (toplevel) ports (capability protocol:runtime:readonly could be added for read-only)
  • Read&write exported ports (capability protocol:runtime provides sending packets)
  • See graph (including edge introspection, currently component:getsource but see #390)
  • Change graph (but not persist, restarts will reset back, capability protocol:graph, requires ability to see graph as well)
  • Persist graph changes (capability network:persist which is not supported by any runtime or client yet)

People who have the secret (passphrase) for the runtime, will always have full rights, including ability to change non-auth access level and secret.

@jonnor jonnor added the ux label May 31, 2014
@bergie bergie added a commit to noflo/noflo.github.io that referenced this issue Sep 26, 2014
@bergie bergie Document the secret token, refs noflo/noflo-ui#278 noflo/noflo-ui#372 2d0b453
@bergie bergie added a commit to noflo/noflo.github.io that referenced this issue Mar 26, 2015
@bergie bergie Protocol v0.5: improved access control support, refs noflo/noflo-ui#278 d12f99d
@bergie bergie added a commit to noflo/noflo-runtime-base that referenced this issue Mar 26, 2015
@bergie bergie Add capability checks everywhere, refs noflo/noflo-ui#278 8810422
@bergie bergie added a commit to flowbased/fbp-protocol-client that referenced this issue Mar 26, 2015
@bergie bergie FBP protocol v0.5 support, refs noflo/noflo-ui#278 84cbbd9
@bergie bergie added a commit to noflo/noflo-runtime-websocket that referenced this issue Mar 26, 2015
@bergie bergie Provide canDo and getPermitted, refs noflo/noflo-ui#278 7ea8fca
@bergie bergie referenced this issue in noflo/noflo-nodejs Mar 26, 2015
Open

multiple users for a runtime #4

@bergie bergie added a commit to noflo/noflo-runtime-websocket that referenced this issue Mar 26, 2015
@bergie bergie Allow defining default permissions by CLI, refs noflo/noflo-ui#278 293d0ff
@bergie bergie closed this Aug 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment