warden_openid_bearer 0.1.1 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9783cc4309a4ebdd46af9ba25ac4f503778b90cca7cf2e9024bbca1f7e1a8f05
-  data.tar.gz: 407df835c53bcb051ff8f088da057185675b568079e0ba9cebcb750644a990b4
+  metadata.gz: 7d1514a1fefcebd1c255a74d18df49f546d103ca7382e52464777f12c32f34e7
+  data.tar.gz: 91c9843e458d7bf1cedc6f360f54f40a28b67eddc9891b9fe364251c6a1c78a0
 SHA512:
-  metadata.gz: 1f263483de3ea8ba723041a1ac2262a6b5a9bf6c14ca458e6db0c3f5e16edeb38f48f0a316e841c72e959d26ce05b676079f18a604549b83ce4eccdfead73237
-  data.tar.gz: b7ac91b59d75793872e6ce809a3f7fb0f27a0e4a8305080815ae52ed0c437d017a26acc9877939319dc0310206da777e41ffeed0669c5be67a35afe1e69ec37d
+  metadata.gz: 7d82af75ad73daffb395154b35ecefef6196078e6bfc9333d0c8d8f59a9e218100d163fcd4f0a7c6f67098bc81d47a8bc92a0a1a2f26149ddca491f02bb3bce4
+  data.tar.gz: 870825f9e3f800506a1c4b45ecd2783da72e8077c5a47a74abe2b4e3dc434c43ac8998cbbfe5f861aae5d964b39ebfd3aff42fd74f9aa12d070e794a17cf8f49

data/CHANGELOG.md

@@ -1,4 +1,8 @@
-## [Unreleased]
+## [0.1.3] - 2022-10-07
+- Fix `require`s
+
+## [0.1.2] - 2022-10-07
+- Fix gemspec dependencies
 
 ## [0.1.1] - 2022-10-07
 - Now with documentation

data/lib/warden_openid_bearer/cache_mixin.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module WardenOpenidBearer
   # We don't need an overengineered approach based on the Rails cache.
   # No, really.

data/lib/warden_openid_bearer/discovered_config.rb

@@ -1,3 +1,7 @@
+# frozen_string_literal: true
+
+require "net/http"
+
 module WardenOpenidBearer
   # Cacheable configuration (periodically re-)fetched starting from
   # the OpenID authentication server's “well-known” endpoint

data/lib/warden_openid_bearer/registerer.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 require "warden"
 
 module WardenOpenidBearer

data/lib/warden_openid_bearer/strategy.rb

@@ -1,21 +1,25 @@
-# Like `WardenOpenidAuth::Strategy` in
-# `lib/warden_openid_auth/strategy.rb` from the `warden_openid_auth`
-# gem, except done right for a modern, split-backend Web application
-# (in which the browser takes charge of the OAuth2 login dance, and
-# the back-end only checks signatures on the JWT claims).
-#
-# You shoud subclass `WardenOpenidBearer::Strategy` and override the
-# `user_of_claims` protected method if you want `env['warden'].user`
-# to be a “real” user object (instead of just a hash of OIDC claims,
-# which is what happens when using `WardenOpenidBearer::Strategy` directly).
-# If you want your Rails app to support more than one OIDC
-# authentication server, you should also subclass
-# `WardenOpenidBearer::Strategy` and override the `metadata_url` method.
-#
-# This class has a `self.register!` method, which makes things
-# (slightly) easier than calling `Warden::Strategies.add` yourself.
-# See `WardenOpenidBearer::Registerer` for details.
+# frozen_string_literal: true
+
+require "jwt"
+
 module WardenOpenidBearer
+  # Like `WardenOpenidAuth::Strategy` in
+  # `lib/warden_openid_auth/strategy.rb` from the `warden_openid_auth`
+  # gem, except done right for a modern, split-backend Web application
+  # (in which the browser takes charge of the OAuth2 login dance, and
+  # the back-end only checks signatures on the JWT claims).
+  #
+  # You shoud subclass `WardenOpenidBearer::Strategy` and override the
+  # `user_of_claims` protected method if you want `env['warden'].user`
+  # to be a “real” user object (instead of just a hash of OIDC claims,
+  # which is what happens when using `WardenOpenidBearer::Strategy` directly).
+  # If you want your Rails app to support more than one OIDC
+  # authentication server, you should also subclass
+  # `WardenOpenidBearer::Strategy` and override the `metadata_url` method.
+  #
+  # This class has a `self.register!` method, which makes things
+  # (slightly) easier than calling `Warden::Strategies.add` yourself.
+  # See `WardenOpenidBearer::Registerer` for details.
   class Strategy < Warden::Strategies::Base
     include WardenOpenidBearer::Registerer # Provides self.register!
     include WardenOpenidBearer::CacheMixin

data/lib/warden_openid_bearer/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module WardenOpenidBearer
-  VERSION = "0.1.1"
+  VERSION = "0.1.3"
 end

data/warden_openid_bearer.gemspec

@@ -42,4 +42,6 @@ Gem::Specification.new do |spec|
 
   spec.add_dependency "warden", "~> 1.2.0"
   spec.add_dependency "dry-configurable", "~> 0.15.0"
+  spec.add_dependency "net-http", "~> 0.2.2"
+  spec.add_dependency "jwt", "~> 2.5"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: warden_openid_bearer
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.3
 platform: ruby
 authors:
 - Dominique Quatravaux
@@ -38,6 +38,34 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 0.15.0
+- !ruby/object:Gem::Dependency
+  name: net-http
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.2.2
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.2.2
+- !ruby/object:Gem::Dependency
+  name: jwt
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.5'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.5'
 description: |2+
 
   This gem is like the `warden_openid_auth` gem, except that it only