Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Google Embraces OAuth Authentication For Apps

Adoption parallels security moves at other sites, including Twitter, Salesforce.com, and Microsoft Azure.




Image Gallery: The Top 16 Google Services
(click for larger image and for full photo gallery)
Google announced Monday that it has embraced OAuth for Google Apps, replacing a less secure system for developers.

"Until today, Google Apps administrators had to sign requests for calls to Google Apps APIs using their username and password (this is called ClientLogin Authorization)," said Ankur Jain, a Google software engineer, in a blog posting.

Now, however, like a number of other websites, Google is adding support for OAuth. Jain said that OAuth will provide Google Apps users with better security, as well as more customized access. "Using OAuth, you can create tokens that scripts may only use to access data of a particular scope when calling Google Apps APIs," he said. For example, a user could approve an email migration tool without giving the tool full access to their Google Apps account.

Google said that six application programming interfaces (APIs) now support OAuth: provisioning, email migration, admin settings, calendar resource, email settings, and audit. The functionality is available to administrators for Google Apps Premier, Education, and Government Editions.

OAuth, short for Open Authorization, is an open standard that allows third-party software to request access rights and act on behalf of a user, without having to submit that user's username and password. Instead, tokens are used to grant access rights to specific content or functionality, sometimes for a specified period of time, or for some sites, such as Twitter, indefinitely.

This decentralized identity management system is especially useful for websites that see large levels of third-party traffic, such as Twitter and Facebook. Indeed, according to Twitter, "the majority of Tweets are sent or read on applications built by the developer community," which was behind the company's reasoning to mandate that all developers switch to using OAuth by last month (after a short delay for the World Cup), in what some dubbed the "OAuthcalypse."

With Salesforce.com, Microsoft Azure, Twitter, and now Google among the large players that have adopted OAuth, the authentication mechanism has obviously reached critical mass, at least in the Web 2.0 world. Now, many sites are also adopting the next version. Facebook, for example, already uses the OAuth 2.0 protocol, and Salesforce.com plans to deploy it globally within the next two weeks.

But going forward, OAuth 2.0 may need work. In particular, earlier this month, Yahoo's director of standards development, Eran Hammer-Lahav, who helped develop OAuth, said that OAuth 2.0 works fine, but only with propriety web service APIs -- for example, to support a Google Apps user, or a Salesforce.com user. But when one site wants to communicate with another, the security could break down, since it depends on client-side enforcement of security, making it essentially "as secure as a cookie."

"None of this matters today," he said, but "as soon as we try to introduce discovery or interoperable APIs across services, OAuth 2.0 fails."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3493
PUBLISHED: 2021-04-17
The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities on files in an underlying file system. Due to the combination of unprivileged user namespaces along with a patch carried in the Ubuntu kernel to allow unprivile...
CVE-2021-3492
PUBLISHED: 2021-04-17
Shiftfs, an out-of-tree stacking file system included in Ubuntu Linux kernels, did not properly handle faults occurring during copy_from_user() correctly. These could lead to either a double-free situation or memory not being freed at all. An attacker could use this to cause a denial of service (ker...
CVE-2020-2509
PUBLISHED: 2021-04-17
A command injection vulnerability has been reported to affect QTS and QuTS hero. If exploited, this vulnerability allows attackers to execute arbitrary commands in a compromised application. We have already fixed this vulnerability in the following versions: QTS 4.5.2.1566 Build 20210202 and later Q...
CVE-2020-36195
PUBLISHED: 2021-04-17
An SQL injection vulnerability has been reported to affect QNAP NAS running Multimedia Console or the Media Streaming add-on. If exploited, the vulnerability allows remote attackers to obtain application information. QNAP has already fixed this vulnerability in the following versions of Multimedia C...
CVE-2021-29445
PUBLISHED: 2021-04-16
jose-node-esm-runtime is an npm package which provides a number of cryptographic functions. In versions prior to 3.11.4 the AES_CBC_HMAC_SHA2 Algorithm (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDe...