omniauth-rpi 1.4.0 → 1.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 046a13f18b0d6b5121129f3ec0cf88659d436e24d0cdabc5637ade5a9408c4f2
-  data.tar.gz: bb10408d0250aa1626d3395a7bf7bbd623257016de74e95dfb627e72c037bb16
+  metadata.gz: 0acde99bd71facbc4acea203fe7bcc55108a3d20590014767508e62bc4b94c48
+  data.tar.gz: d6399c883ce979b5454cd6e2386d6e55bc9bb55882a225b58e9702ef84264e07
 SHA512:
-  metadata.gz: f93f200a4a0fead592af06a75b1c3b475a1458ac8fc9d839855df462c50e0065db1e8fd6bea15e9c1a531f08f409302c6dd3fcfcc3aff45a7ac5555226e3fe77
-  data.tar.gz: f4a68e290ac2eb698ae52cae050de5b8878e782e741506f5f6f52a5ff9f8194bc39a0501da9fdc4eaa77e6395a0eb0c13d3b18a70fab143c3edb6fbb3a892f85
+  metadata.gz: 9faf259dbf1f13018814c48ec9d36ea7a2e0cf5c3dcff1051c46ce96398ed043d1d82cde6d4f102a583db2708ed0a56f891c24a529e6153b6cdb74780bdbee4b
+  data.tar.gz: 855c3fb971c7e605f982df173d96aa7fc67c423d54d5a318d012d61a021aac77fc6dac2aaaa116b821a6883a9637bc1fb0a73275c30eeb9bee3b1fe18df7b832

data/CHANGELOG.md

@@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.4.1] - 2025-7-17
+### Changed
+- jwt version constraint relaxed; see https://github.com/RaspberryPiFoundation/omniauth-rpi/pull/19 for context
+
 ## [1.4.0] - 2023-02-13
 ### Changed
 - Fixes setting of uid from raw_info using sub (uid was previously blank)

data/README.md

@@ -111,6 +111,20 @@ if ENV['BYPASS_OAUTH'].present?
 end
 ```
 
+## v1 Signup redirects
+
+When a client application using Hydra v1 redirects to Pi Accounts / Profile to have a user sign up (either through the default login route with the user then opting to create an account, or through forcing signup (below)), it is necessary to set the `v1_signup` value in the `login_options` param:
+
+```
+POST /auth/rpi?login_options=v1_signup
+```
+
+This ensures that once the `/signup` route has been requested, upon a successful submission of verification code or token to the `/verify` endpoint, the browser is redirected to `/v1/login` so that the remainder of the auth flow can be completed, signing the user in with Hydra and redirecting back to the client application correctly (rather than just dumping the user at their Profile dashboard).
+
+**Note:** Whilst Hydra v0 routes are still the default in Pi Accounts / Profile, `?login_options=v1_signup` needs to be set for any login path, regardless of whether `force_signup` is also being set, this is to cover cases where a user clicks a log in link but then at the log in UI clicks the create account link instead of logging in.
+
+For the full documentation see: https://digital-docs.rpf-internal.org/docs/codebases/accounts/profile-app/hydra-v1-signup
+
 ## Forcing sign up flow
 
 It's possible to force a redirect to the Pi Accounts sign up page (rather than the default log in page) through:
@@ -119,7 +133,9 @@ It's possible to force a redirect to the Pi Accounts sign up page (rather than t
 POST /auth/rpi?login_options=force_signup
 ```
 
-For the full documentation see: https://github.com/RaspberryPiFoundation/documentation/blob/main/accounts/force-signup.md
+(multiple options can be comma-separated, eg. `?login_options=v1_signup,force_signup`)
+
+For the full documentation see: https://digital-docs.rpf-internal.org/docs/codebases/accounts/profile-app/force-signup
 
 ## Testing
 

data/lib/omniauth-rpi/version.rb

@@ -1,5 +1,5 @@
 module OmniAuth
   module Rpi
-    VERSION = '1.4.0'.freeze
+    VERSION = '1.4.1'.freeze
   end
 end

data/omniauth-rpi.gemspec

@@ -20,7 +20,7 @@ Gem::Specification.new do |spec|
   spec.bindir        = 'bin'
   spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
 
-  spec.add_runtime_dependency 'jwt', '~> 2.2.3'
+  spec.add_runtime_dependency 'jwt', '~> 2.2'
   spec.add_runtime_dependency 'omniauth', '~> 2.0'
   spec.add_runtime_dependency 'omniauth-oauth2', '~> 1.4'
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: omniauth-rpi
 version: !ruby/object:Gem::Version
-  version: 1.4.0
+  version: 1.4.1
 platform: ruby
 authors:
 - Raspberry Pi Foundation
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-03-15 00:00:00.000000000 Z
+date: 2025-07-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: jwt
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.2.3
+        version: '2.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.2.3
+        version: '2.2'
 - !ruby/object:Gem::Dependency
   name: omniauth
   requirement: !ruby/object:Gem::Requirement
@@ -167,7 +167,7 @@ homepage: https://www.raspberrypi.org
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -183,7 +183,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubygems_version: 3.1.4
-signing_key: 
+signing_key:
 specification_version: 4
 summary: Official OmniAuth strategy for Raspberry Pi.
 test_files: []