omniauth_oidc 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 74463844a516326572c11a06efb05d658c8f62a14046ef8348f0940296c16433
-  data.tar.gz: 4756f11d552dc0d39085125210631161eaa6fa5ecf27b2388a0a90becec96abc
+  metadata.gz: 5c8e9e95eb8465a662ba0afb8523278c42147c53eb578352229e78ae4b325312
+  data.tar.gz: 48add3142f15a6a428d925359c908f01eabb52cf54aaee09ed4cf958fcba075a
 SHA512:
-  metadata.gz: 11a227e37b5878b9ac0e61ee4956acc36e905a17271d06bc33992d37aad3e5a6e33f777e6f9118f3b60ada81570b9a2b884876d6db08febfa917de59dd721b4b
-  data.tar.gz: 786fbde9d9929102212c954bee84769f5a8a4d92f36347ec3dfb299d785f94a9a26ffd0057395e96d385a12a6e720aacf42b3b6476cbe3622b5ed394563ff19a
+  metadata.gz: 1d63037d94b36b91ff143458a961676817c3ebe9a20a08dcb1a2252ac9a423fc6612dd5ef9968ebfeec1a8909b1643a53e212d0e38bb835313c82d8867361628
+  data.tar.gz: 6685d6045e34c7595a1cd21c6dfb91332ec07febafd7baae04a3ba58c1a7b25b345324f6d0bc44668ecec274bc502d3444e8eceae76afc53b42b2c1204aa035c

data/CHANGELOG.md

@@ -1,5 +1,8 @@
 ## [Released]
 
+## [0.2.3] - 2024-08-04
+- Update readme
+
 ## [0.2.2] - 2024-08-04
 - Update dependencies, update documentation, fix end_session_uri, update other_phase
 

data/README.md

@@ -236,10 +236,10 @@ options. Here’s a sample setup:
 Using these two configurations, you can ensure that when a user logs out from your application, they are also logged out
 from the OIDC provider, providing a seamless logout across multiple services.
 
-This works by calling `other_phase` on every request in your application, which checks if the requested URL matches the 
-defined `logout_path`. If it does, meaning that the current user has requested to log out from your application, 
-`other_phase` redirects to the `end_session_endpoin`t to terminate the user's session with the OIDC provider if such a 
-session exists. Then it returns back to your application and concludes the request to end the session.
+This works by calling `other_phase` on every controller request in your application. The method checks if the requested 
+URL matches the defined `logout_path`. If it does (i.e. current user has requested to log out from your application) 
+`other_phase` performs a redirect to the `end_session_endpoint` to terminate the user's session with the OIDC provider 
+and then it returns back to your application and concludes the request to end the current user's session.
 
 For additional details please refer to the [OIDC specification](https://openid.net/specs/openid-connect-session-1_0-17.html#:~:text=%C2%A0TOC-,5.%C2%A0%20RP%2DInitiated%20Logout,-An%20RP%20can).
 

data/lib/omniauth/oidc/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module OmniauthOidc
-  VERSION = "0.2.2"
+  VERSION = "0.2.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: omniauth_oidc
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.2.3
 platform: ruby
 authors:
 - Suleyman Musayev