foobara-auth-http 0.1.0 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 62b67f4f6ae5108b39697d7c792e33854f1a9f79d2bd9a00cdd28999a15330be
-  data.tar.gz: 99efd48356f66e58aeb1c387cf54f5b08a3de61bfb7ab68c58a8d88f34e244c7
+  metadata.gz: 016bcd816d77d49551a798013b1f1dc00a2b90999c7495b780d75262e8a847af
+  data.tar.gz: f3ea2ca603b95d0f31d38f46496cc95475a07d0c7fa9eaa1fdbd50f30ea566f0
 SHA512:
-  metadata.gz: d9973773609190f3b369a29dbaba12e67d17b048baf4bd44091a00b3d1491d60328c8af38f42c922bac6187b2d30abc12b8799fe9c8fdf866d2fb62453dfb78e
-  data.tar.gz: db20a0f1870d0048d0cb59f628707470b36af8403c1dd04a718a4459f54fb918f29ab242bfe2962e5c9dc5b8a0e3cab3572a9103a8af415f11edf2a627000a45
+  metadata.gz: 695c59e8167f0289cbc2c81e9d90c81829759fac4ee98ec9ffc5aeae79fea61f3cfadc7701ee08401ae77cb43f508b1521fdc4cf864a3172453bf59a1d5431d1
+  data.tar.gz: 373df4a3e625b0fd16e5a331907c702ff55436a74647613e01f473793688e6e35ffa8709fb2584c89e9b392dffa56492f930c2ec59e408edb24d3661e169e721

data/CHANGELOG.md

@@ -1,3 +1,11 @@
+## [0.1.2] - 2026-02-16
+
+- Add a :logs_out desugarizer
+
+## [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

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

@@ -8,8 +8,9 @@ module Foobara
 
     class << self
       def install!
-        CommandConnectors::Http.register_authenticator(BearerAuthenticator)
-        CommandConnectors::Http.register_authenticator(ApiKeyAuthenticator)
+        CommandConnectors::Http.register_authenticator BearerAuthenticator
+        CommandConnectors::Http.register_authenticator ApiKeyAuthenticator
+        CommandConnectors::Http.add_desugarizer Desugarizers::LogsOut
       end
     end
   end

data/src/desugarizers/logs_out.rb

@@ -0,0 +1,24 @@
+module Foobara
+  module AuthHttp
+    module Desugarizers
+      class LogsOut < CommandConnectors::Desugarizer
+        def applicable?(args_and_opts)
+          args_and_opts.last[:logs_out]
+        end
+
+        def desugarize(args_and_opts)
+          args, opts = args_and_opts
+
+          opts = opts.merge(
+            request_mutators: Foobara::AuthHttp::SetRefreshTokenFromCookie,
+            response_mutators: Foobara::AuthHttp::ClearAccessTokenHeader
+          )
+
+          opts.delete(:logs_out)
+
+          [args, opts]
+        end
+      end
+    end
+  end
+end

data/src/{foobara/auth_http → request_mutators}/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

data/src/{foobara/auth_http → response_mutators}/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 → response_mutators}/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

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: foobara-auth-http
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.2
 platform: ruby
 authors:
 - Miles Georgi
@@ -69,13 +69,14 @@ files:
 - LICENSE.txt
 - README.md
 - lib/foobara/auth_http.rb
-- src/foobara/auth_http/api_key_authenticator.rb
-- src/foobara/auth_http/bearer_authenticator.rb
-- src/foobara/auth_http/clear_access_token_header.rb
-- src/foobara/auth_http/move_access_token_to_header.rb
-- src/foobara/auth_http/move_refresh_token_to_cookie.rb
-- src/foobara/auth_http/set_refresh_token_from_cookie.rb
-- src/foobara/auth_http/set_user_to_authenticated_user.rb
+- src/authenticators/api_key_authenticator.rb
+- src/authenticators/bearer_authenticator.rb
+- src/desugarizers/logs_out.rb
+- src/request_mutators/set_refresh_token_from_cookie.rb
+- src/request_mutators/set_user_to_authenticated_user.rb
+- src/response_mutators/clear_access_token_header.rb
+- src/response_mutators/move_access_token_to_header.rb
+- src/response_mutators/move_refresh_token_to_cookie.rb
 homepage: https://github.com/foobara/auth-http
 licenses:
 - Apache-2.0 OR MIT