Solves Warden compatibility and gives the possibility to register an user after connection established. #429
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.
"current_#{class}"
after successful sign in. The name of the object depends on the model given as authenticable object. Websocket-rails hascurrent_user
hardcoded.connection
:register_user
anddestroy_user
. With this two methods its now possible to register (associate a user to a connection) the current entity (e.g. current_user) after the connection is established (useful in case if you have a non-browser websocket client (c++, java,...) and you want to make the authentication over websocket).Example using Rails 4, Devise 3.2.4, Websocket-Rails: