Generally speaking, every major provider except Microsoft. More specifically, over 50 companies last time I counted which was a year ago when we coordinated 1.0a.
An outdated partial list: http://wiki.oauth.net/ServiceProviders 1.0a signatures are widely deployed, secure, and have plenty of library support. EHL From: Anthony Nadalin [mailto:tony...@microsoft.com] Sent: Monday, September 27, 2010 9:48 PM To: Eran Hammer-Lahav; OAuth WG (oauth@ietf.org) Subject: RE: Proposal: OAuth 1.0 signature in core with revision Still no real answers ... From: Eran Hammer-Lahav [mailto:e...@hueniverse.com] Sent: Monday, September 27, 2010 9:46 PM To: Anthony Nadalin; OAuth WG (oauth@ietf.org) Subject: RE: Proposal: OAuth 1.0 signature in core with revision You must be joking about 1.0a signature deployment. It's also nice that half a day is your measurement for obtaining consensus. EHL From: Anthony Nadalin [mailto:tony...@microsoft.com] Sent: Monday, September 27, 2010 2:38 PM To: Eran Hammer-Lahav; OAuth WG (oauth@ietf.org) Subject: RE: Proposal: OAuth 1.0 signature in core with revision Not seeing an overwhelming support for doing this, how many interoperable deployments of 1.0a signature are there? From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Eran Hammer-Lahav Sent: Sunday, September 26, 2010 11:44 PM To: OAuth WG (oauth@ietf.org) Subject: [OAUTH-WG] Proposal: OAuth 1.0 signature in core with revision Building on John Panzer's proposal, I would like to ask if people have strong objections to the following: - Add the 1.0a RFC language for HMAC-SHA-1 signatures to the core specification in -11 - Discuss the signature language on the list and improve both prose and signature base string construction - Apply improvements to -12 Keeping the 1.0a signature in the core specification makes sense and builds on existing experience and deployment. If we can reach quick consensus on some improvements, great. If not, we satisfy the need of many here to offer a simple alternative to bearer tokens, without having to reach consensus on a new signature algorithm suitable for core inclusion. --- I have seen nothing to suggest that this working group is going to reach consensus on a single signature algorithm worthy of core inclusion. I agree with John that at least the 1.0a algorithm is well understood and already deployed. I can live with it used without changes, which will also allow reusing existing code with 2.0. I think we can improve it by making small changes, but have better things to do with my time than spend the next few months arguing over it. By including the 1.0a text in -11, we will have a feature complete specification that I hope many people here can live with if it doesn't change (which looks more likely). My question is, who here has strong objections to this, and cannot live with the core specification including the 1.0a HMAC-SHA1 algorithm? EHL
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
