My blog post http://self-issued.info/?p=1529 – also tweeted at @selfissued<https://twitter.com/selfissued> – referencing today’s announcement by Microsoft identity team follows.
Identity Convergence and Microsoft’s Ongoing Commitment to Interoperability Please check out this important post today on the Active Directory Team Blog: “For Developers: Important upcoming changes to the v2.0 Auth Protocol<http://blogs.technet.com/b/ad/archive/2016/01/27/for-developers-important-upcoming-changes-to-the-v2-0-auth-protocol.aspx>”. While the title may not be catchy, it’s content is compelling – particularly for developers. The post describes the converged identity service being developed by Microsoft that will enable people to log in either with an individual account (Microsoft Account) or an organizational account (Azure Active Directory). This is a big deal, because developers will soon have a single identity service that their applications can use for both kinds of accounts. The other big deal is that the changes announced are a concrete demonstration of Microsoft’s ongoing commitment to interoperability and support for open identity standards – in this case, OpenID Connect<http://openid.net/connect/>. As the post says: The primary motivation for introducing these changes is to be compliant with the OpenID Connect standard specification. By being OpenID Connect compliant, we hope to minimize differences between integrating with Microsoft identity services and with other identity services in the industry. We want to make it easy for developers to use their favorite open source authentication libraries without having to alter the libraries to accommodate Microsoft differences. If you’re a developer, please do heed the request in the post to give the service a try now as it approaches General Availability (GA). Enjoy!
_______________________________________________ board mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-board
