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

Secure communications #1

Open
4 tasks
MetaFight opened this issue Mar 5, 2017 · 0 comments
Open
4 tasks

Secure communications #1

MetaFight opened this issue Mar 5, 2017 · 0 comments
Labels
enhancement
Milestone
Initial Release

Comments

@MetaFight
Copy link
Contributor

MetaFight commented Mar 5, 2017 •
edited
Loading

Currently, all inter-component communication is unencrypted.

It's unclear whether or not this actually constitutes a privacy issue, but to avoid the (most likely painful) discussion altogether I would like to change this.

This will require:

  • RabbitMQ communication with TLS
  • Web Api communication over HTTPS (and related certificates)
  • Re-exposing anonymised versions of the the PersonSignedIn and PersonSignedOut messages
  • Ensuring the MessageBrokerProxyService WCF service communication is properly secured
@MetaFight MetaFight added this to the Initial Release milestone Mar 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
Initial Release
Development

No branches or pull requests
1 participant
@MetaFight