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.

Sign up for GitHub

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

Jump to bottom

Authenticate with backend #1

Open
mauriciopasquier opened this issue Mar 15, 2017 · 2 comments
Open

Authenticate with backend #1

mauriciopasquier opened this issue Mar 15, 2017 · 2 comments
Assignees
@mauriciopasquier
Labels
enhancement

Comments

@mauriciopasquier
Copy link
Collaborator

mauriciopasquier commented Mar 15, 2017 •
edited
Loading

The bot will need to authenticate against our backend server. We need to decide about auth schemes. What we've talked so far:

  • Each device will have an ID of some kind (UUID, certificate, etc.) so we can track status updates
  • Each user will have an account in the backend, in which they can associate devices through a disposable token
  • This token will be generated from the UI, and configured in the device during boot
@mauriciopasquier mauriciopasquier self-assigned this Apr 18, 2017
@mauriciopasquier
Copy link
Collaborator Author

mauriciopasquier commented Apr 18, 2017 •
edited
Loading

Each bot will have a client certificate, and will connect with TLS to our RabbitMQ backend.

  • RabbitMQ server with TLS support
  • Certificate management, validation and auth in bot
  • Token generation in vaquitapp
  • Queues configuration in RabbitMQ
  • Token/User association in vaquita

@mauriciopasquier
Copy link
Collaborator Author

RabbitMQ server is working and online. TLS support is not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mauriciopasquier mauriciopasquier

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mauriciopasquier