Home / Companies / Google Cloud / Blog / Post Details
Content Deep Dive

Reminder to migrate to OAuth 2.0 or OpenID Connect

Blog post from Google Cloud

Post Details
Company
Date Published
Author
-
Word Count
308
Language
English
Hacker News Points
-
Summary

In a 2015 announcement, William Denniss, Product Manager for Identity and Authentication, emphasized the necessity of migrating from deprecated authentication protocols such as ClientLogin, OAuth 1.0 (3LO), AuthSub, and OpenID 2.0 to newer standards like OAuth 2.0 and OpenID Connect by April 20, 2015, to maintain connectivity with Google services. The transition to these modern standards, which enhance security and simplify development, can be facilitated through Google's Sign-in SDKs, which support Web, Android, and iOS platforms. Failure to migrate by the deadline would result in application outages, affecting functionalities such as user sign-in until the migration is completed. Developers were advised to consult Stack Overflow for technical assistance, highlighting that for certain deprecated protocols like AuthSub and ClientLogin, a fresh integration using OAuth 2.0 is necessary, requiring users to re-consent.