Google Online Security Blog: OAuth for Secure Mashups

Security Blog

The latest news and insights from Google on security and safety on the Internet

Posted by Eric Sachs, Senior Product Manager, Google SecurityOAuthAuthSub
However, with the development of a common Internet standard in OAuth, we see much greater potential for data portability and secure mash-ups. Today we announced that the gadget platform now supports OAuth, and the interoperability of this standard was demonstrated by new iGoogle gadgets that AOL and MySpace both built to enable users to see their respective AOL or MySpace mailboxes (and other information) while on iGoogle. However, to ensure the user's privacy, this only works after the user has authorized AOL or MySpace to make their data available to the gadget running on iGoogle. We also previously announced that third-party developers can build their own iGoogle gadgets that access the OAuth-enabled APIs for Google applications such as Calendar, Picasa, and Docs. In fact, since both the gadget platform and OAuth technology are open standards, we are working to help other companies who run services similar to iGoogle to enhance them with support for these standards. Once that is in place, these new OAuth-powered gadgets that are available on iGoogle will also work on those other sites, including many of the gadgets that Google offers for its own applications. This provides a platform for some interesting mash-ups. For example, a third-party developer could create a single gadget that uses OAuth to access both Google OAuth-enabled APIs (such as a Gmail user's address book) and MySpace OAuth-enabled APIs (such as a user's friend list) and display a mashup of the combination.
While the combination of OAuth with gadgets is an exciting new use of the technology, most of the use of OAuth is between websites, such as to enable a user of Google Health to allow a clinical trial matching site to access his or her health profile. I previously mentioned that one privacy control provided by OAuth is that it defines a standard way for users to authorize one website to make their data accessible to another website. In addition, OAuth provides a way to do this without the first site needing to reveal the identity of the user -- it simply provides a different opaque security token to each additional website the user wants to share his or her data with. It would allow a mutual fund, for example, to provide an iGoogle gadget to their customers that would run on iGoogle and show the user the value of his or her mutual fund, but without giving Google any unique information about the user, such as a social security number or account number. In the future, maybe we will even see industries like banks use standards such as OAuth to allow their customers to authorize utility companies to perform direct debit from the user's bank account without that person having to actually share his or her bank account number with the utility vendor.
The OAuth community is continuing to enhance this standard and is very interested in having more companies engaged with its development. The OAuth.net website has more details about the current standard, and I maintain a website with advanced information about Google's use of OAuth, including work on integrating OAuth with desktop apps, and integrating with federation standards such as OpenID and SAML. If you're interested in engaging with the OAuth community, please get in touch with us.

Google

1 Kommentar :

PROGRESANDOWEB hat gesagt…: buen aporte aqui les dejo mi enlace: www.progresandoweb.blogspot.com; 25. November 2008 um 23:30

Kommentar veröffentlichen

Labels

#sharethemicincyber
#supplychain #security #opensource
AI Security
android
android security
android tr
app security
big data
biometrics
blackhat
C++
chrome
chrome enterprise
chrome security
connected devices
CTF
diversity
encryption
federated learning
fuzzing
Gboard
google play
google play protect
hacking
interoperability
iot security
kubernetes
linux kernel
memory safety
Open Source
pha family highlights
pixel
privacy
private compute core
Rowhammer
rust
Security
security rewards program
sigstore
spyware
supply chain
targeted spyware
tensor
Titan M2
VDP
vulnerabilities
workshop

Archive

2025
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2024
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2023
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2022
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2021
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2020
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2019
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2018
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2017
- Dez.
- Nov.
- Okt.
- Sept.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2016
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2015
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2014
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Apr.
- März
- Feb.
- Jan.

2013
- Dez.
- Nov.
- Okt.
- Aug.
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2012
- Dez.
- Sept.
- Aug.
- Juni
- Mai
- Apr.
- März
- Feb.
- Jan.

2011
- Dez.
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Juni
- Mai
- Apr.
- März
- Feb.

2010
- Nov.
- Okt.
- Sept.
- Aug.
- Juli
- Mai
- Apr.
- März

2009
- Nov.
- Okt.
- Aug.
- Juli
- Juni
- März

2008
- Dez.
- Nov.
- Okt.
- Aug.
- Juli
- Mai
- Feb.

2007
- Nov.
- Okt.
- Sept.
- Juli
- Juni
- Mai

Feed

Follow

Give us feedback in our Product Forums.

Google
Privacy
Terms