sorcery-jwt 0.1.12 → 0.1.13

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0c71e86aea70bc6ac73748a70f36bfb7a164fb3a0dec9f0da0a0cd44231d0501
-  data.tar.gz: 0b4fe6f65d2673638ffef90745adf129e1392e62862a3e5ed0c8bffbd8a9b1de
+  metadata.gz: adb4d9ffaf4afc6d3fcec35d9101b699d8985b5304c2767625781b0a8e76b8ac
+  data.tar.gz: 5281e03b1e243165b870433dea084976bf2955bd97d8ee3dcc8dea2904d459f6
 SHA512:
-  metadata.gz: 7f4be3b1b2463be77b321c1fd0cc214f9a95c7df520f466d1c19362cb9c5ede64c8056a4a50646ac7c10b408fe6e6b26492acf70993f38c88d6716bd8e025ab2
-  data.tar.gz: 00ab9a77fedd8f3fb6806c4a5c7d3c47e463f4d7423cc28c023806e7761a39ca66a4a9fd38e639eeb6c54c0930e04d8039b4068f6955490418f5546beea8e3e7
+  metadata.gz: 410e26d8ac465776c84d9cbb5e84fdc266d7adefa87c6b1d97ad9ae7a542eb2b1c1dd820ecbdcceb6ee7c461883ce4d2bad47b322797ed8529c50a82c36956d5
+  data.tar.gz: '08f4afb85fa904eb01e5542d335f00baabcd1a331b3f0fb56f188844052ce2b98252ed54d4fa0f8b5ab37de53e8cc544e8509b42eb5413c2d7f0056b28aa702c'

data/README.md

@@ -2,6 +2,8 @@
 
 Jwt extension for the Sorcery authentication library
 
+# NOTE: Sorcery v1 is being developed and JWT is being implemented as a core plugin. See https://github.com/Sorcery/sorcery-rework/issues/9 for more.
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -42,7 +44,7 @@ end
 
 Available algorithms are listed at https://github.com/jwt/ruby-jwt.
 
-You're now ready to start using the library. By including the submodule, each request will check for an authorization header with a JWT as the value. If the JWT is valid, it will set the `current_user` in the controller to the matching user. It is up to you to handle what happens when a token is invalid or JWTs need to be revoked. Some ideas here: http://waiting-for-dev.github.io/blog/2017/01/24/jwt_revocation_strategies/.
+You're now ready to start using the library. By including the submodule, each request will check for an authorization header with a JWT as the value. If the JWT is valid, it will set the `current_user` in the controller to the matching user. It is up to you to handle what happens when a token is invalid or JWTs need to be revoked. Some ideas here: http://waiting-for-dev.github.io/blog/2017/01/24/jwt_revocation_strategies.
 
 To login a user and issue a token, use the `login_and_issue_token` method from a controller. This method takes the same `email` and `password` arguments that the Sorcery `authenticate` method does.
 

data/lib/sorcery/jwt/version.rb

@@ -1,5 +1,5 @@
 module Sorcery
   module Jwt
-    VERSION = "0.1.12".freeze
+    VERSION = "0.1.13".freeze
   end
 end

data/sorcery-jwt.gemspec

@@ -42,5 +42,5 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency "rspec", "~> 3.0"
 
   spec.add_runtime_dependency "jwt", ">= 1.0", "< 3.0"
-  spec.add_runtime_dependency "sorcery", ">= 0.13", "< 0.16"
+  spec.add_runtime_dependency "sorcery", ">= 0.13", "< 0.17"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: sorcery-jwt
 version: !ruby/object:Gem::Version
-  version: 0.1.12
+  version: 0.1.13
 platform: ruby
 authors:
 - Hayden Luckenbach
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-05-17 00:00:00.000000000 Z
+date: 2022-02-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -95,7 +95,7 @@ dependencies:
         version: '0.13'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '0.16'
+        version: '0.17'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -105,7 +105,7 @@ dependencies:
         version: '0.13'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '0.16'
+        version: '0.17'
 description: ''
 email:
 - hluckenb@gmail.com
@@ -148,7 +148,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.3
+rubygems_version: 3.1.6
 signing_key:
 specification_version: 4
 summary: Jwt extension for the Sorcery authentication library