[CL-921] Attempt to fix verification error for Clave Unica (Chile) an…

…d Bosa FAS (Belgium)

This is an attempt to fix the verification error we are seeing in Sentry for Bosa FAS and Clave Unica.

Specifically I'm eyeballing the fix introduced in 0.4 here omniauth/omniauth_openid_connect#97. The stack trace matches what we see in Sentry:

https://sentry.hq.citizenlab.co/organizations/citizenlab/issues/45980/?referrer=jira_integration
https://sentry.hq.citizenlab.co/organizations/citizenlab/issues/46899/?project=2&query=is%3Aunresolved&statsPeriod=14d

  This is hard to test locally because the documentation at https://www.notion.so/citizenlab/SSO-ID-Verification-263b705ca14e472c8e41b444663e373a#1da11c08825c441687faf4be31fb14f8 is lacking and far as I know we do not have a working sandbox environment for any of the two verification methods. I'd therefore like to blindly deploy it to production and ask Pablo again to verify on a Chilean platform for me.

back/Gemfile

@@ -133,7 +133,7 @@ gem 'simple_segment', '~>1.2'
 # This fork was made to update the version of jws which is
 # required for the google omniauth gem.
 gem 'omniauth-azure-activedirectory', github: 'CitizenLabDotCo/omniauth-azure-activedirectory'
-gem 'omniauth_openid_connect', '~> 0.3.3'
+gem 'omniauth_openid_connect', '~> 0.4.0'
 # Forked to support a userinfo response in JWT form
 # Can go back to vanilla when this PR is merged and released:
 # https://github.com/nov/openid_connect/pull/48

back/engines/commercial/id_clave_unica/id_clave_unica.gemspec

@@ -16,7 +16,7 @@ Gem::Specification.new do |s|
 
   s.add_dependency 'rails', '~> 6.1'
   s.add_dependency 'verification'
-  s.add_dependency 'omniauth_openid_connect', '~> 0.3.3'
+  s.add_dependency 'omniauth_openid_connect', '~> 0.4.0'
 
   s.add_development_dependency 'rspec_api_documentation'
   s.add_development_dependency 'rspec-rails'