omniauth-fortnox-oauth2 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e867e1c0804b077222e57ec5d0bb96da3fcc642047b435949b65783dcec3e177
-  data.tar.gz: 465953deef868451d8670e3056d99a8ce38c8bb1ba5904dd2d5ec05cf3ab57ab
+  metadata.gz: 8b4205196f555885b665f46c8133c393375e402004fd5f649afdeb37550baf53
+  data.tar.gz: c801df59317f0ea20f13c128e14bc37e9805d921987057f2ad4dd10c54f43037
 SHA512:
-  metadata.gz: c38c7b304242bcf94d265e29a5c42e59e223ccaa790105eddc0b09b63190768fa61eb99a9798ea26d5e83180f91a1a1cc4c31b425f1191ed1923ee9bd59f6260
-  data.tar.gz: 43a72b8c8ce885db697f5a8bf0702a4549fe28b956f3f55e3bea76965168acbbfaf3ad53ec011235b5f347c097d9d73aa74233758eac5d1567234130d4bc85e3
+  metadata.gz: 965555b3e2b1fd7ab763875cb58f460b1979777df3b4e09fd9c7cd9a3552288ea27bec775256e027f6b907067bcb87e5618d8358edaff06bf92b08d4e3120e8e
+  data.tar.gz: b853caf7304547f7660366a0f43c0637a16edf0221516432a8e35bb506323dc7c8037b495af8e4e41e073fcaf367c489f0b6adf7dd2192bf19fd83b25e421bd3

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    omniauth-fortnox-oauth2 (0.0.3)
+    omniauth-fortnox-oauth2 (0.0.4)
       omniauth-oauth2
 
 GEM

data/README.md

@@ -79,17 +79,6 @@ You can also configure the `client_options` by passing in any of the following s
 
 * `token_method`: Override the token_method used by the gem, default `:post`.
 
-## Note
-Currently the only way to support multiple redirect uri's in Fortnox is to add them sperated using ` ` (space). This will work for the initial request to get the authorization code.
-When trading the code for a token the `redirect_uri` will be matched using the string used in Fortnox developer portal. This is beeing changed but for now the workaround is to pass that string.
-This can here be passed as an option `fortnox_redirect_uri`, it can contain one or multiple uri's.
-This will need to exactly match the string in Fortnox.
-
-For example:
-```ruby
-env['omniauth.strategy'].options[:fortnox_redirect_uri] = 'https://test.test/callback https://second-test.test/callback'
-```
-
 ## Auth Hash
 
 Here's an example of an authentication hash available in the callback by accessing `request.env['omniauth.auth']`:

data/lib/omniauth/fortnox_oauth2/version.rb

@@ -2,6 +2,6 @@
 
 module Omniauth
   module FortnoxOAuth2
-    VERSION = '0.0.3'
+    VERSION = '0.0.4'
   end
 end

data/lib/omniauth/strategies/fortnox_oauth2.rb

@@ -67,21 +67,12 @@ module OmniAuth
         options[:callback_url] || (full_host + script_name + callback_path)
       end
 
-      # Currently the only way to support multiple redirect uri's in Fortnox
-      # is to add them sperated using ` ` (space). This will work for the
-      # initial request to get the authorization code.
-      # When trading the code for a token the `redirect_uri` will be matched
-      # using the string entered in Fortnox developer portal. This is beeing
-      # changed but for now the workaround is to pass that string.
-      # It can contain one or multiple uri's.
-      #
       def build_access_token
-        redirect_uri = options.fortnox_redirect_uri || callback_url
         verifier = request.params['code']
 
         client.auth_code.get_token(
           verifier,
-          { redirect_uri: redirect_uri }.merge(token_params.to_hash(symbolize_keys: true)),
+          { redirect_uri: callback_url }.merge(token_params.to_hash(symbolize_keys: true)),
           deep_symbolize(options.auth_token_params)
         )
       end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: omniauth-fortnox-oauth2
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - svenne87
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-05-10 00:00:00.000000000 Z
+date: 2023-05-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: omniauth-oauth2