17fcdd60c1
All the data we need for the `info` and `credentials` auth hash are obtained via the user info API, not the JWT. Using and verifying the JWT can fail due to clock skew, so let's skip it completely. PR opened to fix the upstream issue at https://github.com/zquestz/omniauth-google-oauth2/pull/392 |
||
|---|---|---|
| .. | ||
| auth_provider.rb | ||
| authenticator.rb | ||
| current_user_provider.rb | ||
| default_current_user_provider.rb | ||
| discord_authenticator.rb | ||
| facebook_authenticator.rb | ||
| github_authenticator.rb | ||
| google_oauth2_authenticator.rb | ||
| managed_authenticator.rb | ||
| oauth2_authenticator.rb | ||
| result.rb | ||
| twitter_authenticator.rb | ||