omniauth-google-id-token 1.1.3 → 1.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2b9cb7b7839da58f2239f9224c664972d865e66956088790db7275548664ce76
-  data.tar.gz: 8ad8ad7214c796bc2836e79b0b3e58f9ab98eb50e20b2fbaaa188be7e07d015a
+  metadata.gz: 935df22bbb30216ef788fd2ca70a1b41fe8eeb00668861019cb6df02e0f6323e
+  data.tar.gz: 65e44a9a715f39ae15094d4d38a0247b07a666e1b0d8f0a84f87bd9ba8c14eb4
 SHA512:
-  metadata.gz: 50ed1f84e0399305cbb0e4903e92fce1a83e8c2e238f3490accc1a427e86517348537f94ccacd46db2ff92fbe41b80123b3736dfcd5f825cccbe8771236b726b
-  data.tar.gz: 9329c75e85089d0d5935e7713e073a540bc36bed65b971ad26114ad3463ea7057d6c86373bfcf5b2174d89bfd95e3ce5dd6e45cbfe1ccaf60aac94e064598853
+  metadata.gz: c70f4af7a562d110079e62ca2356e406317184467d47f8035b9f049e43fd7f9a5279b4d744a8a602da2ebf39ab6fe24e938b4bd4eff2a5034c2b520b7bcb4290
+  data.tar.gz: 30ed3ce0405a67f921a33a5dcbfea7afdf774c19dca780d304b5cf38183b88f01c20a99530d8af103ea1ed1606a1b7d99fdd5fcf568d20d505c7b835aeff818d

data/README.md

@@ -1,3 +1,8 @@
+# I haven't update readme yet, please read source make sure you use right option.
+
+`lib/omniauth/strategies/google_id_token.rb`
+
+
 # OmniAuth::GoogleIdToken
 
 A [omnitauth](https://github.com/omniauth/omniauth) strategy primarily used for validating Google ID tokens
@@ -31,7 +36,21 @@ Or install it yourself as:
 You use OmniAuth::Strategies::GoogleIdToken just like you do any other OmniAuth strategy:
 
 ```ruby
-use OmniAuth::Strategies::GoogleIdToken, aud_claim: '123.apps.googleusercontent.com', azp_claim: '123.apps.googleusercontent.com'
+Rails.application.config.middleware.use OmniAuth::Builder do
+  provider :developer, :callback_path => "/nexus-api/auth/developer/callback", provider_ignores_state: true if Rails.env.development?
+  # provider :google-oauth2, ENV['GOOGLE_CLIENT_ID'], ENV['GOOGLE_CLIENT_SECRET'], scope: 'email, profile', provider_ignores_state: true , :callback_path => "/nexus-api/auth/google-oauth2/callback"
+    
+  
+  provider :'google-id-token', client_id: ENV['GOOGLE_CLIENT_ID']
+  # or
+  # to rename the provider
+  use OmniAuth::Strategies::GoogleIdToken,name: "google-oauth2",  client_id: ENV['GOOGLE_CLIENT_ID']
+  
+  
+end
+
+OmniAuth.config.allowed_request_methods = %i[get post]
+
 ```
 
 If this strategy is used primarily for validating a Google ID token, then the only required fields are
@@ -45,34 +64,28 @@ response section.
 * **name:** The name of the strategy. The default name is `google_id_token` but it can be changed to any value, for
   example `google`. The OmniAuth URL will thus change to `/auth/google` and the `provider` key in the auth hash will
   then return `google`.
-* **cert:** the x509 certificate can be provided to manually define a certificate to validate the tokens.
-* **expiry:** Expiry defines the the time (in seconds) in which the cached Google certificates are valid.
 * **uid_claim:** this determines which claim will be used to uniquely identify the user. Defaults
-  to `email`
+  to `sub`
 * **client_id:** The client ID string that you obtain from the [API Console](https://console.developers.google.com/),
   as described in [Obtain OAuth 2.0 credentials](https://developers.google.com/identity/protocols/OpenIDConnect#getcredentials)
-* **aud_claim:** Identifies the audience that this ID token is intended for. It must be one of the OAuth 2.0 client
-  IDs of your application
-* **azp_claim:** The client_id of the authorized presenter. This claim is only needed when the party requesting the
-  ID token is not the same as the audience of the ID token. This may be the case at Google for hybrid apps where a
-  web application and Android app have a different client_id but share the same project.
 * **required_claims:** array of claims that are required to make this a valid authentication call.
   Defaults to `['name', 'email']`
+* **scope:** array of request data in google api. Defaults to `['name', 'email', 'openid']`
 * **info_map:** array mapping claim values to info hash values. Defaults to mapping `name` and `email`
   to the same in the info hash.
 
 ### Authentication Process
 
-When you authenticate through `omniauth-google-id-token` you can send users to `/auth/googleidtoken`
+When you authenticate through `omniauth-google-id-token` you can send users to `/auth/google-id-token`
 and it will redirect them to the URL https://accounts.google.com/o/oauth2/auth (and example can be
 found at https://developers.google.com/identity/protocols/OAuth2WebServer#handlingresponse
 Sample OAuth 2.0 server response).
 
 From there, Google generates a ID token and sends to the redirect_uri passed in URL query params.
-The redirect_uri will look like '/auth/googleidtoken/callback`. This is the endpoint to send the id token
+The redirect_uri will look like '/auth/google-id-token/callback`. This is the endpoint to send the id token
 to if coming from a mobile or web app looking to validate a user with the backend server:
 
-    /auth/googleidtoken/callback?id_token=ENCODEDJWTGOESHERE
+    /auth/google-id-token/callback?id_token=ENCODEDJWTGOESHERE
 
 ## Contributing
 

data/lib/omniauth/google_id_token/version.rb

@@ -1,5 +1,5 @@
 module OmniAuth
   module GoogleIdToken
-    VERSION = '1.1.3'.freeze
+    VERSION = '1.1.4'.freeze
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: omniauth-google-id-token
 version: !ruby/object:Gem::Version
-  version: 1.1.3
+  version: 1.1.4
 platform: ruby
 authors:
 - Joshua Morris
@@ -9,7 +9,7 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-11-09 00:00:00.000000000 Z
+date: 2023-11-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler