hayfever / sorcery-jwt Goto Github PK

in Gemfile:

gem 'sorcery', '~> 0.16'

bundle update sorcery
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
Bundler could not find compatible versions for gem "sorcery":
  In Gemfile:
    sorcery (~> 0.16)

    sorcery-jwt was resolved to 0.1.12, which depends on
      sorcery (>= 0.13, < 0.16)

Sorcery resolved ruby 2.7.x deprecation warnings (among other things) starting in version 0.16.0: https://github.com/Sorcery/sorcery/releases/tag/v0.16.0
Sorcery/sorcery#241

I realize https://github.com/Sorcery/sorcery-rework will support jwt, but appears to be stalled. Can we catch up with core sorcery in the meantime?

Thanks so much for all your JWT work!

The link to jwt_revocation_strategies is sadly no longer working.

The login_and_issue_token method is limited to controllers, so can't be used in GraphQL mutations

I tried to log out using the sorcery method (logout) but it just updates some columns from the user but if I continue using the JWT token it will be valid until it expired by the date, not respecting the logout method.
Any idea?

Hi,

I have a simple setup of sorcery and sorcery-jwt with following details.

Rails.application.config.sorcery.submodules = [:jwt, :reset_password, :user_activation, :activity_logging]
.....
.....
.....

config.user_config do |user|
   user.jwt_secret = Rails.application.credentials.dig(Rails.env.to_sym, :jwt_key)
    user.jwt_algorithm = 'HS256' # HS256 is used by default.
end

On controller

class ApiController < ActionController::API
end

class TokensController < ApiController
  def create
    token = login_and_issue_token(params[:email], params[:password])
    json_response(token, 200)
  end
end

When controller action is called it throw following error.

NoMethodError: undefined method `login_and_issue_token' for #\u003cTokensController:0x00007ffbd60a0b20\u003e\u003e"

If I already have a user, say from an oauth login, is it possible to retrieve the token for that user?

I tried @token = login_and_issue_token(@user.email, @user.crypted_password)
but that just returns nil.