zaikio-jwt_auth 0.2.0 → 0.2.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 608b4341e5cb5797a302e65439882e050044fd2676b0fc01f7931783529ee032
-  data.tar.gz: 1dcaeb58daa1f352c352b8a3e65bab7e46618c4dba30f64af2141c25bb1f2dee
+  metadata.gz: c12ee3b69a3ce0152c39d0af1a5af71bc79ac24651b622e7cfa411c851c8d35f
+  data.tar.gz: 48e86c7cf283611de01b8754b5125f16545107c576a544c0c91c9d78be8ebac7
 SHA512:
-  metadata.gz: 2289f1f2fc4ddc1a84070f6df75ebbfb143b4b0634ff8a64d3c54cfa5fb2741de8734aaa398989fd9fb63a43dde8ccb4849fa497eee8f6e3a1897acd5fde4dcf
-  data.tar.gz: 4b935055a6461f2f2e22dec109634e41b40222773fb363811e76d29327eea22d81210a470e6d9865092473d114c1c21646a99bcbb0942cdc4e39229f7f4e8291
+  metadata.gz: 22cbcb8445e7c8a7bc56aff7516a4dbce5f5763b41a37599fd123957950883af076f5138d40ceef37ee9a0d8d121e36adb924ac1d9d06aaf4f1df4e762cede4d
+  data.tar.gz: 1d2d5d926d21a79eb734b6ddfd1b4c03f8b7b17b4fc8261bc11dba58722adea46340cb2901c24ac0588553a5d78048145d4ded1e84333246db4e9dfa023b8ca3

data/README.md

@@ -61,6 +61,8 @@ class API::ResourcesController < API::ApplicationController
 end
 ```
 
+By convention, `authorize_by_jwt_scopes` automatically maps all CRUD actions in a controller. Requests for `show` and `index` with a read or read_write scope are allowed. All other actions like `create`, `update` and `destroy` are accepted if the scope is a write or read_write scope. Therefore it is strongly recommended to always create standard Rails resources. If a custom action is required, you will need to authorize yourself using the `after_jwt_auth`.
+
 ### 6. Optionally, if you are using SSO: Check revoked tokens
 
 Additionally, the API provides a method called `revoked_jwt?` which expects the `jti` of the JWT.
@@ -73,10 +75,23 @@ Zaikio::JWTAuth.revoked_jwt?('jti-of-token') # returns true if token was revoked
 
 ```rb
 # in your test_helper.rb
-include Zaikio::JWTAuth::TestHelper
+class ActiveSupport::TestCase
+  # ...
+  include Zaikio::JWTAuth::TestHelper
+  # ...
+end
+
+# in your integration tests you can use:
+class ResourcesControllerTest < ActionDispatch::IntegrationTest
+  def setup
+    mock_jwt(sub: 'Organization/123', scope: ['directory.organization.r'])
+  end
 
-# in your tests you can use:
-mock_jwt(sub: 'Organization/123', scope: ['directory.organization.r'])
+  test "do a request with a mocked jwt" do
+    get resources_path
+    # test the actual business logic
+  end
+end
 ```
 
 ## Advanced

data/config/initializers/inflections.rb

@@ -0,0 +1,3 @@
+ActiveSupport::Inflector.inflections(:en) do |inflect|
+  inflect.acronym "JWT"
+end

data/lib/zaikio/jwt_auth.rb

@@ -32,9 +32,10 @@ module Zaikio
     def self.blacklisted_token_ids
       return [] if mocked_jwt_payload
 
-      return configuration.blacklisted_token_ids if configuration.blacklisted_token_ids
-
-      DirectoryCache.fetch("api/v1/blacklisted_access_tokens.json", expires_after: 60.minutes)["blacklisted_token_ids"]
+      configuration.blacklisted_token_ids || DirectoryCache.fetch(
+        "api/v1/blacklisted_access_tokens.json",
+        expires_after: 60.minutes
+      )["blacklisted_token_ids"]
     end
 
     def self.included(base)
@@ -76,7 +77,7 @@ module Zaikio
 
         return if show_error_if_authorize_by_jwt_scopes_fails(token_data)
 
-        send(:after_jwt_auth, token_data) if respond_to?(:after_jwt_auth)
+        send(:after_jwt_auth, token_data) if respond_to?(:after_jwt_auth, true)
       rescue JWT::ExpiredSignature
         render_error("jwt_expired") && (return)
       rescue JWT::DecodeError

data/lib/zaikio/jwt_auth/configuration.rb

@@ -31,7 +31,7 @@ module Zaikio
       end
 
       def keys
-        @keys.is_a?(Proc) ? @keys.call : @keys
+        defined?(@keys) && @keys.is_a?(Proc) ? @keys.call : @keys
       end
 
       def blacklisted_token_ids

data/lib/zaikio/jwt_auth/test_helper.rb

@@ -1,7 +1,7 @@
 module Zaikio
   module JWTAuth
     module TestHelper
-      def after_setup
+      def after_teardown
         Zaikio::JWTAuth.mocked_jwt_payload = nil
         super
       end

data/lib/zaikio/jwt_auth/version.rb

@@ -1,5 +1,5 @@
 module Zaikio
   module JWTAuth
-    VERSION = "0.2.0".freeze
+    VERSION = "0.2.5".freeze
   end
 end

metadata

@@ -1,14 +1,16 @@
 --- !ruby/object:Gem::Specification
 name: zaikio-jwt_auth
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.5
 platform: ruby
 authors:
-- Crispy Mountain GmbH
+- crispymtn
+- Jalyna Schröder
+- Martin Spickermann
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-03-27 00:00:00.000000000 Z
+date: 2020-06-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: oj
@@ -30,14 +32,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 6.0.2.2
+        version: 5.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 6.0.2.2
+        version: 5.0.0
 - !ruby/object:Gem::Dependency
   name: jwt
   requirement: !ruby/object:Gem::Requirement
@@ -54,7 +56,9 @@ dependencies:
         version: 2.2.1
 description: JWT-Based authentication and authorization with zaikio.
 email:
+- op@crispymtn.com
 - js@crispymtn.com
+- spickermann@gmail.com
 executables: []
 extensions: []
 extra_rdoc_files: []
@@ -63,6 +67,7 @@ files:
 - README.md
 - Rakefile
 - app/jobs/zaikio/jwt_auth/revoke_access_token_job.rb
+- config/initializers/inflections.rb
 - lib/tasks/zaikio/jwt_auth_tasks.rake
 - lib/zaikio/jwt_auth.rb
 - lib/zaikio/jwt_auth/configuration.rb
@@ -92,7 +97,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.2
+rubygems_version: 3.0.3
 signing_key: 
 specification_version: 4
 summary: JWT-Based authentication and authorization with zaikio