We're always moving to bring more value and improve the experience of working with the Myspace Developer Platform to you, our developers. As we've upgraded our APIs to support OAuth 2.0 we've also been looking at the experience of developing experiences that leverage the Myspace platform outside the walls of Myspace.
The current off-site login tools, collectively known as Myspace ID, are just too complicated and have too many similar options. Currently we support two different off-site login mechanisms through MySpace ID and our MySpace ID SDKs:
As we roll out our OAuth 2.0 support, that's going to add a third login option - OAuth 2.0 client login. Time and again our developers have shown us that what they want is to validate users in order to leverage their social graph data through our rich API catalog. The best solution to this problem is OAuth Login. In order to focus on delivering the best experience to our developers, we're going to phase out support for OpenID login from Myspace ID so we can focus solely on OAuth login solutions moving forward.
OpenID support will continue to function for a time period in order to allow our developers time to transition to using OAuth login. If you are currently using one of the Myspace ID SDKs, this should be a relatively simple matter; the SDKs currently include support for both OAuth login and OpenID login. In the coming months we will be removing OpenID support from the SDKs in order to eliminate confusion and retiring OpenID support.
In the mean time, you are encouraged to explore and transition to OAuth login, enjoy the simpler implementation, cleaner interface, and mobile device support. Happy coding!