{"_id":"547e44d8b3f56708000b8e9a","initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"__v":0,"project":"545137a814af501a00b50cf9","tags":[],"user":{"_id":"5451763614af501a00b50e08","username":"","name":"Shana McFadden"},"createdAt":"2014-12-02T23:01:44.111Z","changelog":[],"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Yammer OAuth 1.0 to OAuth 2.0 Upgrade – Action Required\"\n}\n[/block]\nOn September 30th, 2014, we will be ending support of OAuth 1.0 authentication. After this date, all Yammer third party applications (apps) will only be able to use OAuth 2.0 authentication and authorization. We have identified there are about 90 Yammer apps using OAuth 1.0 out of 100,000 Yammer third party apps. To avoid any service interruption, we highly encourage the Yammer customers who are still using OAuth 1.0 in their apps to transition to OAuth 2.0 as soon as possible.\n\nAll third party apps require authorization in order to access user data. This authorization can only be obtained when a third party app requests user authorization using Yammer’s authentication flow. Yammer authentication is an OAuth 2.0 standard flow that is initiated from the apps. Compared to OAuth 1.0, OAuth 2.0 handles scale significantly better than 1.0. Since 2012, OAuth 2.0 authorization flows have been widely adopted as a new industry standard. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices. For authorizing all third party apps to access user data in Yammer, please see the following guidance to make that transition: supported OAuth 2 authorization flows.\n\nWhat is the impact to Yammer customers?\nAll Yammer third party apps will no longer be able to use the OAuth 1.0 authorization flow to get new tokens to access user data over the Yammer REST API. When customers access any Yammer third party apps, they will receive a “bad request” response if they use OAuth 1.0.\n\nWho will be impacted?\nOnly Yammer customers using Yammer third party apps that still rely on OAuth 1.0 will be impacted. Apps that use OAuth 2.0 flows will not be affected.\n\nWhat is the required action for the impacted customers?\nAll Yammer third Party apps developers should transition their apps to an OAuth 2.0 authorization flow following the steps that are provided on Yammer Authentication page on the Yammer Developer site.\n\n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n\n\nBy The Yammer Platform Team.\nPosted on August 25, 2014","slug":"blog-2","title":"Yammer OAuth 1.0 Changes"}

Yammer OAuth 1.0 Changes


[block:api-header] { "type": "basic", "title": "Yammer OAuth 1.0 to OAuth 2.0 Upgrade – Action Required" } [/block] On September 30th, 2014, we will be ending support of OAuth 1.0 authentication. After this date, all Yammer third party applications (apps) will only be able to use OAuth 2.0 authentication and authorization. We have identified there are about 90 Yammer apps using OAuth 1.0 out of 100,000 Yammer third party apps. To avoid any service interruption, we highly encourage the Yammer customers who are still using OAuth 1.0 in their apps to transition to OAuth 2.0 as soon as possible. All third party apps require authorization in order to access user data. This authorization can only be obtained when a third party app requests user authorization using Yammer’s authentication flow. Yammer authentication is an OAuth 2.0 standard flow that is initiated from the apps. Compared to OAuth 1.0, OAuth 2.0 handles scale significantly better than 1.0. Since 2012, OAuth 2.0 authorization flows have been widely adopted as a new industry standard. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices. For authorizing all third party apps to access user data in Yammer, please see the following guidance to make that transition: supported OAuth 2 authorization flows. What is the impact to Yammer customers? All Yammer third party apps will no longer be able to use the OAuth 1.0 authorization flow to get new tokens to access user data over the Yammer REST API. When customers access any Yammer third party apps, they will receive a “bad request” response if they use OAuth 1.0. Who will be impacted? Only Yammer customers using Yammer third party apps that still rely on OAuth 1.0 will be impacted. Apps that use OAuth 2.0 flows will not be affected. What is the required action for the impacted customers? All Yammer third Party apps developers should transition their apps to an OAuth 2.0 authorization flow following the steps that are provided on Yammer Authentication page on the Yammer Developer site. [block:api-header] { "type": "basic" } [/block] By The Yammer Platform Team. Posted on August 25, 2014