locked
Google as identidy provider not working anymore s of May 19, 2014 RRS feed

  • General discussion

  • fyi:

    As of May 19, 2014, new ACS namespaces cannot use Google as an identity provider. ACS namespaces that used Google and were registered before this date are unaffected. For more information, see Release Notes.

    see here: http://msdn.microsoft.com/en-us/library/hh674478.aspx  and here http://leandrob.com/2014/06/windows-azure-acs-open-id-google-authentication-broken-or-the-difference-between-a-serious-cloud-service-and-windows-azure-acs/


    further text

    As of May 19, 2014, new ACS namespaces cannot use Google as an identity provider. ACS namespaces that used Google and were registered before May 19, 2014 are unaffected. This new limitation exists because Google is phasing out support for OpenID 2.0, which ACS depends on, and has closed registration for new applications. Existing ACS namespaces that used Google will continue to work until April 20, 2015. If your application requires support for Google accounts, we recommend that you register your application with them directly. For more information, see Google's documentation.

    Monday, August 25, 2014 7:43 PM