OmniAuth google oauth update
- You just updated a couple of gems including the omniauth google oauth one ?
- Your oauth callback is now failing ?
Well, don't worry it's not too bad.
Google decided to deprecate some of its OAuth endpoints and OmniAuth updated its code before the September deadline.
Yet, as there is little documentation about this changes a lot of us went through a difficult time.
The solution is simple : activate the Google+ API for your account.
It was documented in an issue : https://github.com/zquestz/omniauth-google-oauth2/issues/111#issuecomment-44718385 , and @olivierlacan introduced a CHANGELOG in a PR to document such changes : https://github.com/zquestz/omniauth-google-oauth2/issues/132 .
Written by Thomas Riboulet
Related protips
1 Response
May save a lot of hassle of worrying about the nitty-gritty if you use oauth.io as described here: https://coderwall.com/p/7dixyg/javascript-google-social-login-button-for-oauth
Have a fresh tip? Share with Coderwall community!
OAuth buttons are third-party code running on your origin. A compromised script beside that button can tamper with the redirect or capture the session the login just created.
Security insights from Cside