Live Connect

Announcements

• Messenger Connect v4.1 is now deprecated

  Dare Obasanjo - MSFT Saturday, June 25, 2011 12:25 AM

  With the release of v5.0 of the Messenger Connect API, the previous version is now deprecated. As mentioned in the v5.0 announcement blog post, the latest version of the Messenger Connect API is the result of taking into account a lot of the input from developers about how to simplify the API and address key limitations we had in the previous version. 

  The v4.1 API will continue to function and will be supported for one year after the release of the v5.0 API. New applications are strongly encouraged to use the v5.0 Messenger Connect instead of the deprecated v4.1 API. It is also recommended that when you upgrade or modify existing applications avoid using and remove usage of the v4.1 APIs. 

  Below is a list of v4.1 features that will no longer be supported in new applications with the release of v5.0 of the Messenger Connect API 

   

  • The v4.1 API provides the ability to publish activities using activity streams to a user’s Messenger Social feed. We received significant feedback from developers and end users that this functionality is not complete because it doesn’t set the Messenger status field and is thus not visible in the user contact list nor in mobile or previous versions of the Messenger client. In addition, we’ve gotten complaints about the complexity of the data formats required to publish status updates. For this reason, we have updated the activity object available in v5.0   to address these shortcomings. For this reason we are not supporting any new applications using the v4.1 activity publishing APIs although this will continue to function in existing applications. Any new applications that try to use this functionality from the v4.1 APIs will receive a 1073 error. 

   

  In summary, the v4.1 Messenger Connect APIs are deprecated and will cease to work on June 25, 2012. 

   

• Live Connect v5.0 released

  Dare Obasanjo - MSFT Wednesday, June 15, 2011 5:11 PM

  Thanks for all the feedback on v4.1. We've made a number of changes based on your feedback. You can find out what they are by visiting 

  • http://windowsteamblog.com/windows_live/b/windowslive/archive/2011/06/14/windows-live-developer-platform-adds-oauth-2-0-and-more-continuing-to-let-users-connect-the-devices-apps-and-sites-they-choose.aspx
  • http://dev.live.com  

• Live Connect Code Samples on GitHub

  Steve Gordon - MSFT Tuesday, August 02, 2011 8:54 PM
  Thanks to the feedback we received from the community after shipping v5.0, we have created a repo on GitHub with code samples for a variety of platforms, including Windows Phone, Windows, iOS, PHP, and ASP.NET. Check it out: https://github.com/liveservices/LiveSDK

• Support Operation Hours for Live Connect Forum

  Navdeep Bawa-MSFTMicrosoft EmployeeMonday, April 09, 2012 11:03 PM

  This forum is monitored by Live Connect Support and Product Group team.

  Hours of Operation: 8:00AM – 5:00PM US Pacific Time (Monday – Friday)

  We do not provide any support over the weekend (Saturday-Sunday).

  Thanks!!!

  Live Connect Support Team

• Changes in OAuth Endpoints

  Navdeep Bawa-MSFTMicrosoft EmployeeTuesday, April 17, 2012 5:32 PM

  We would like to inform you of about the changes to the OAuth 2.0 SDK.  We have transitioned the OAuth endpoints to https://login.live.com. This change is to move our OAuth 2.0 authentication service to be on the same backend as our primary login infrastructure. It will give increased scalability and reliability to our OAuth interface and also add some security features like invalidating refresh tokens if the users are detected as compromised or has changed their password.   

  The https://oauth.live.com endpoints will continue to function but with slightly increased latency so we recommend you begin using the new URL’s.

  The new endpoints are:

  • authorization: https://login.live.com/oauth20_authorize.srf
  • token: https://login.live.com/oauth20_token.srf
  • desktop: https://login.live.com/oauth20_desktop.srf

  The old end points are:

  • authorization: https://oauth.live.com/authorize     
  • token: https://oauth.live.com/token
  • desktop: https://oauth.live.com/desktop