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

Authentication for V2 #3

Open
daltoniam opened this issue Jan 11, 2017 · 0 comments
Open

Authentication for V2 #3

daltoniam opened this issue Jan 11, 2017 · 0 comments

Comments

@daltoniam
Copy link
Member

The team has discussed and our current thoughts are to add a simple authentication interface to simplify adding authentication and security conductor instances. This will include:

Creating a interface that can be implemented that will have functions that check for authentication on:

  • Check if a client can connect to the conductor instance. This will be done through HTTP headers on the upgrade. The client will send their auth_token along which can be validated if the user can connect to the instance or not. This will also all a simple form of user identification.

  • Binding to a stream. The server can ensure the user has permission to bind and message to a stream.

  • Invite opcode. This is useful in requesting a client bind to a stream and has knowledge of said stream. The difficulty of this opcode will be how to properly deal with the concept of a "user" vs client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant