JWT identification #23
Draft
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
palkan
force-pushed
the
demo/jwt-identification
branch
14 times, most recently
from
e7d4a04 to
f3bed35
Compare
palkan
force-pushed
the
demo/jwt-identification
branch
from
f3bed35 to
72785ca
Compare
palkan
force-pushed
the
demo/jwt-identification
branch
from
72785ca to
3e4ad51
Compare
palkan
force-pushed
the
demo/anycable-client
branch
from
72c301d to
5ff9620
Compare
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.
Description
This PR demonstrates the usage if the JWT identification feature from AnyCable Go PRO along with the AnyCable Client library and the anycable-rails-jwt gem.
This PR is based on #21.
Changes
anycable-rails-jwtgemaction_cable_meta_tagwithaction_cable_with_jwt_meta_tagtokenRefresherconfiguration tocreateCable(utils/cable.js).