foobara-auth-http 0.0.7 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ef6f90acea12cf50d2ec6660e562f2406a7579a7406607856e80da9fdf22985d
-  data.tar.gz: 77c991a02c4678dd57a4ef5b5f64dde3ee6a1d90c1c8c73d7586175aa1c78f1a
+  metadata.gz: b560d7ee6971787591dc89f1633fbf2e7a94342201e8a9dcf0e64590decc28bb
+  data.tar.gz: 4c7ea4a062a2e58e332fba9a83d300cbb47000db2f3e0566704a8bd5329c9895
 SHA512:
-  metadata.gz: d9e8467e3af3c8c3ee0e2edce731fa11719148cd855526ad7e1a65579bbdab457c56de77f92ac00e9cbe549ada464a6380e6a0ebb414cc92172b3ed5386c328b
-  data.tar.gz: d8bd18c51108559e9957a66f3c0953942d692000ff350ed4c3ea54ee86c219c455055518f02cdda13163b5c0d5314990d61acb0adba3d67113a42599d647813e
+  metadata.gz: 909ad7cbc1048851904c69aec412fec01980fbfb8eb5978ef699c8820b266c38dbd6110ab188de206baf934258b551131ec64d48de7d03434c59f3db846ec777
+  data.tar.gz: 3f6944615986d90e65f5baa943d8f73f016b264b259f729ff0881652ca5fcce7860dc7eac12ac148423c92ebcca2f4ce30c451cdaaef0cb90deb944254490925

data/CHANGELOG.md

@@ -1,3 +1,11 @@
+## [0.1.1] - 2026-01-27
+
+- Use lower-case header keys to appease Rack::Lint
+
+## [0.1.0] - 2025-08-22
+
+- Mark as compatible with Foobara 0.1.0
+
 ## [0.0.7] - 2025-05-03
 
 - Expose relevant entity classes from authenticators for better transaction automation

data/README.md

@@ -75,13 +75,13 @@ A rundown of everything happening here:
 * We are declaring that we want to authenticate using bearer tokens. These are JWT tokens in an
   `Authorization: Bearer <token>` header.
 * We are declaring that when we login or refresh our login, we would like to move the new access token
-  from the result to an X-Access-Token header, and we would like
+  from the result to an x-access-token header, and we would like
   to move the new refresh token from the result to a secure http only cookie.
 * We are declaring that when we want to refresh our login, we want to move the refresh token from the
   headers to an input to RefreshLogin.
 * Logout could technically be handled by the client but for convenience/added safety, we expose
   Logout and move the refresh token to its inputs so that it can invalidate the refresh token.
-* When we respond from Logout, we set the X-Access-Token header to nil. This is something the client
+* When we respond from Logout, we set the x-access-token header to nil. This is something the client
   could do but gives an easy way to clobber the client's access token without effort on their end.
 
 We also expose a few app commands using our authenticator. This is configured as part of command connectors not

data/lib/foobara/auth_http.rb

@@ -16,4 +16,4 @@ module Foobara
 end
 
 Foobara::Util.require_directory "#{__dir__}/../../src"
-Foobara::Monorepo.project "auth_http", project_path: "#{__dir__}/../../"
+Foobara.project "auth_http", project_path: "#{__dir__}/../../"

data/src/foobara/auth_http/clear_access_token_header.rb

@@ -8,7 +8,7 @@ module Foobara
         end
       end
 
-      def initialize(header_name = "X-Access-Token", header_value = nil)
+      def initialize(header_name = "x-access-token", header_value = nil)
         super()
 
         self.header_name = header_name.to_s

data/src/foobara/auth_http/move_access_token_to_header.rb

@@ -8,7 +8,7 @@ module Foobara
         end
       end
 
-      def initialize(attribute_name = :access_token, header_name = "X-Access-Token")
+      def initialize(attribute_name = :access_token, header_name = "x-access-token")
         super()
 
         self.attribute_name = attribute_name.to_sym

data/src/foobara/auth_http/set_user_to_authenticated_user.rb

@@ -1,5 +1,6 @@
 module Foobara
   module AuthHttp
+    # Is this genuinely a generic enough concept to be a class in this project?
     class SetUserToAuthenticatedUser < Foobara::CommandConnectors::Http::SetInputToProcResult
       # TODO: move this into base class as default?
       class << self

metadata

@@ -1,56 +1,62 @@
 --- !ruby/object:Gem::Specification
 name: foobara-auth-http
 version: !ruby/object:Gem::Version
-  version: 0.0.7
+  version: 0.1.1
 platform: ruby
 authors:
 - Miles Georgi
 bindir: bin
 cert_chain: []
-date: 2025-05-03 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: foobara
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 0.0.116
+        version: 0.1.1
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.1.1
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 0.0.116
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: foobara-auth
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 0.0.1
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 0.0.1
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: foobara-http-command-connector
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 0.0.1
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 0.0.1
+        version: 2.0.0
 email:
 - azimux@gmail.com
 executables: []
@@ -92,7 +98,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.2
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Contains convenience classes/methods for using Foobara::Auth over HTTP
 test_files: []