Google Sign-In Change

As of today, we have removed support for signing in to Hoop.la, UBB Forum, and QuestionShark via direct Google sign-in. Previously, there were separate sign-in mechanisms for Google and Google+. One of the benefits of the previous Google sign-in implementation was that it used OpenID 2.0, which meant it required zero configuration for community admins.

 

Google has deprecated and will soon be removing all support for OpenID 2.0 sign-ins. As a result of this change, it's now impossible to support the zero configuration option for community admins. In the interest of simplifying the configuration options, we are completely removing the standalone Google sign-in option in favor of supporting Google+ as the only Google-enabled sign-in option.

 

If your site did not have Google sign-ins enabled previously, this change will not impact your community in any way.

 

If your site did have Google sign-ins enabled previously, any members who have used Google to sign-in will be affected. We have sent automated messages to all affected users of your community to let them know about this sign-in change. We made the process as simple as possible in that we included a direct link to set a new account password in this email for users who have not yet set a password on their account.

 

Going forward, if you want to support Google sign-ins on your community, you will simply need to use the Google+ sign-in option. You can find this in your control panel under Social Networks. In order to enable Google+ sign-ins, you will need to register your community with Google's APIs via their developer console.

 

If you have any questions or concerns about any of this, please open a new support topic, and we'll be happy to help you.

Add Comment

Comments (0)

×
×
×
×