Authenticate socket connections #116
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 8 commits
April 29, 2015 23:27
[ci skip]
from-the-river-to-the-sea
pushed a commit
that referenced
this pull request
May 6, 2015
Authenticate socket connections
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When login security is enabled, all socket connections are authenticated by a key. Each user on each passport strategy has their own key, and it functions very similarly to a Twitch stream key. The user can view and regenerate their key at any time from the dashboard.
For dashboard access, this change is invisible to the user as the key is automatically injected. To access a view url, the user must append their key as a URL param, such as
localhost:9090/view/lange-notify?key=xxxxxxxxxx