The Google announcement of this new OpenID service has now been formally posted at<br><div style="margin-left: 40px;"><a href="http://googlecode.blogspot.com/2009/07/google-apps-openid-identity-hub-for.html">http://googlecode.blogspot.com/2009/07/google-apps-openid-identity-hub-for.html</a><br>
</div><br><div class="gmail_quote">On Wed, Jul 8, 2009 at 11:47 AM, Eric Sachs <span dir="ltr"><<a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yes, I now realize I mistakenly posted this to the public instead or private board mailing list :-) Not a particularly big deal since we have been discussing this planned launch in the discovery community.<div>
<br></div><div>
Feel free to respond on either the public or private mailing list.</div><div><div></div><div><br><div class="gmail_quote">On Wed, Jul 8, 2009 at 11:05 AM, Eric Sachs <span dir="ltr"><<a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>Below are drafts of two blog posts we will make in the upcoming weeks about the fact that we are now operating an OpenID IDP for the million+ schools/enterprise/ISPs that are outsourcing their email to Google Apps. We would appreciate this not being circulated beyond the board until it is public. This new support required that we work with the community to define some extensions to the OpenID discovery process. While those discussions have been going on in the community the last few months, those extensions are not yet formalized and probably won't be until they are proven in production environments. There is the potential for some community members (or press) to assume (or at least imply in articles) some evil intent by Google to co-opt OpenID with these extensions. It would be nice to have a blog post on the formal OpenID blog that was supportive of our approach, so I wanted to see if the board members are comfortable with that.</div>
<div><br></div><div>On a somewhat related point, I also expect this will further increase the pressure on us as a community to find more scalable UI options since the Nascar style approach obviously cannot include buttons for these million new IDPs. We have also just posted a set of summary UI guidelines that we will be referencing from our API documentation at <a href="http://sites.google.com/site/oauthgoog/UXFedLogin/summary" target="_blank">http://sites.google.com/site/oauthgoog/UXFedLogin/summary</a>. The goal was to keep it to one-page which forced us to cut additional background information, but if you think we cut something critical, let me know.</div>
<br><div><span style="font-family: Verdana;"><div style="margin-top: 0px; margin-bottom: 0px;"><h3 style="font-size: 12pt;">Enterprise blog: Google Apps + OpenID = identity hub for all your SaaS</h3>
<p style="margin: 0px;">We are happy to announce that the <a href="http://code.google.com/apis/apps/sso/openid_reference_implementation.html" title="Google OpenID Federated Login API" target="_blank">Google OpenID Federated Login API</a> has been extended to Google Apps accounts used by businesses, schools, and other organizations. The service is important not only to the individuals in those organizations, who can interact with a variety of consumer websites with a single credential <<span style="background-color: rgb(255, 255, 0);">add link to Google code post</span>>, but also to the organizations themselves, who are increasingly reliant on multiple Software as a Service (SaaS) solutions from different vendors.</p>
<p style="margin: 0px;"><br></p>For these organizations, Google Apps can now become an identity and data hub for multiple SaaS providers. When integrated with partner solutions such as XXX from XXX, the Google Open ID Federated Login API enables a single Google Apps login to provide secure access to services like Salesforce.com, SuccessFactors, and WebEX, as well as B2B partners, internal applications, and of course consumer web sites. See XXX's post <<span style="background-color: rgb(255, 255, 0);">add link</span>> to learn more about their implementation and view the demo and case study <<span style="background-color: rgb(255, 255, 0);">add links</span>>.<p style="margin: 0px;">
<br></p><p style="margin: 0px;">Another early adopter is XXX, a SaaS project management vendor who uses the new service to make it easier for any organization using Google Apps to sign up for and deploy XXX o their users:<br>
</p><br><div style="margin-top: 0px; margin-bottom: 0px; text-align: center;"><div style="margin-top: 0px; margin-bottom: 0px; text-align: center;">< INSERT SCREEN SHOTS><br><br><br></div><div style="margin-top: 0px; margin-bottom: 0px; text-align: left;">
Activating the OpenID Federated Login service for your domain is simple and secure. To achieve that, we introduced a new experimental <a href="http://groups.google.com/group/google-federated-login-api/web/openid-discovery-for-hosted-domains" title="discovery protocol" target="_blank">discovery protocol</a> addressing some of the challenges with the <a href="http://openid.net/specs/openid-authentication-2_0.html" title="current version (2.0) of OpenID" target="_blank">current version (2.0) of OpenID</a>:</div>
</div><p style="margin: 0px;"> </p></div><div style="margin-top: 0px; margin-bottom: 0px;"><ul style="margin-top: 0px; margin-bottom: 0px;"><li style="margin-top: 0px; margin-bottom: 0px;">
Reducing the hassle of hosting discovery documents on the domain web-site - the discovery protocol offer a solution that allows a hosted domain to become an OpenID Provider without hosting any documents at all. Optionally, a domain may choose to host one simple file to support a more complete discovery flow.</li>
</ul><br><ul style="margin-top: 0px; margin-bottom: 0px;"><li style="margin-top: 0px; margin-bottom: 0px;">Being an OpenID Identity Provider requires strong security protection again attacks that could modify web pages on the site. To avoid that requirement for businesses and organizations, we introduced digital signatures on the discovery documents and a verification flow to support that.</li>
</ul><br>You can find more details in our <a href="http://code.google.com/apis/apps/sso/openid_reference_implementation.html" title="API" target="_blank">API</a> and <a href="http://groups.google.com/group/google-federated-login-api/web/openid-discovery-for-hosted-domains" title="Discovery" target="_blank">Discovery</a> documentation, or join the discussions in the <a href="http://groups.google.com/group/google-federated-login-api/web/oauth-support-in-googles-federated-login-api" title="Google Federated Login API Group" target="_blank">Google Federated Login API Group</a>, where you can ask any question and get answers from with other Identity Providers, Relying Parties and Google engineers.<br>
<p style="margin: 0px;"><br></p><b>The OpenID Federated Login Service is available for all Google Apps editions. However, it is disabled by default for the Premier and Education and editions , and it requires the Domain Admin to manually enable it from the Control Panel. So Admins - <a title="go turn this today for your users" href="http://code.google.com/apis/apps/sso/openid_reference_implementation.html#cpanel" target="_blank">go turn this today for your users</a>. At Google.com - we already enabled it for our employees... </b><br>
<br><br><h3 style="font-size: 12pt;">Google Code blog: Over a million new OpenID Identity Providers !</h3>We are happy to announce that the <a href="http://code.google.com/apis/apps/sso/openid_reference_implementation.html" title="Google OpenID Federated Login API" target="_blank">Google OpenID Federated Login API</a> has been extended to Google Apps accounts used by businesses, schools, and other organizations. Individuals in these organizations can now sign in to 3rd party websites using their Google Apps account, without giving away their credentials. In addition to the value for the end-users, the new service also benefits the organizations themselves, who are increasingly reliant on multiple Software as a Service (SaaS) solutions from different vendors. For example, XXX<font size="2"> is an early adopter, allowing any organization running Google Apps to more quickly sign up for and adopt their service:<br>
<br></font><div style="margin-top: 0px; margin-bottom: 0px; text-align: center;"><< INSERT SCREEN SHOTS></div></div><div style="margin-top: 0px; margin-bottom: 0px;"><br><br>See our post on the Google Enterprise Blog <<span style="background-color: rgb(255, 255, 0);">add link</span>> to learn more about the opportunities for the organizations. <br>
</div><div style="margin-top: 0px; margin-bottom: 0px;"><p style="margin: 0px;"><br></p><p style="margin: 0px;">
Supporting the API for Google Apps accounts is exciting news for the <a href="http://www.openid.net/" title="OpenID community" style="color: rgb(85, 26, 139);" target="_blank">OpenID community</a>, as it adds numerous new trustworthy Identity Provider (IDP) domains and increases the OpenID end user base by millions. In order to allow web-sites to easily become Relying Parties for these many new IDPs and users, we defined a new <a href="http://groups.google.com/group/google-federated-login-api/web/openid-discovery-for-hosted-domains" title="discovery protocol" target="_blank">discovery protocol</a>. The protocol allows Relying Parties to identify that a given domain is hosted on Google Apps and securely access its OpenID Provider End Point. The current proposal is an interim solution, and we are participating in several standardization organizations, such as <a href="http://www.oasis-open.org/" title="OASIS" target="_blank">OASIS</a> and the <a href="http://openid.net/foundation/" title="OpenID Foundation" style="color: rgb(85, 26, 139);" target="_blank">OpenID Foundation</a>, to generate a next-generation standard. Since the current protocol proposal is not supported by the standard OpenID libraries, we provided an implementation of the Relying Party pieces at the Open Source project - <a href="http://code.google.com/p/step2/" title="step2.googlecode.com" style="color: rgb(85, 26, 139);" target="_blank">step2.googlecode.com</a>. Google is also offering a set of resource addressing the issues of designing a scalable Federated Login User Interface. You are welcome to visit the <a title="User Experience summary for Federated Login" href="http://sites.google.com/site/oauthgoog/UXFedLogin/summary" style="color: rgb(85, 26, 139);" target="_blank">User Experience summary for Federated Login</a> Google Sites page, where you can find links do demos, mocks and usabilty research data. <br>
</p></div><div style="margin-top: 0px; margin-bottom: 0px;"><br>Prefer an out-of-the-box solution? We have been working with <a href="http://www.janrain.com/" title="JanRain" style="color: rgb(85, 26, 139);" target="_blank">JanRain</a>, a provider of OpenID solutions, which already support the new API as part of their <a href="http://rpxnow.com/" title="RPX product" style="color: rgb(85, 26, 139);" target="_blank">RPX product</a>. As demonstrated by <a href="http://uservoice.com/session/new" title="UserVoice" style="color: rgb(85, 26, 139);" target="_blank">UserVoice</a> using <a href="http://rpxnow.com/" title="Janrain's RPX" target="_blank">JanRain's RPX</a>, a user simply types in her Google Apps hosted domain name in the OpenID login box and everything else is being taken care of:<p style="margin: 0px;">
<br></p><p style="margin: 0px;"><span style="background-color: rgb(255, 255, 0);"><Add UserVoice (or other proposed RPX website) screenshots></span></p>
<p style="margin: 0px;"> </p><br>You can find more details in our <a href="http://code.google.com/apis/apps/sso/openid_reference_implementation.html" title="API" target="_blank">API</a> and <a href="http://groups.google.com/group/google-federated-login-api/web/openid-discovery-for-hosted-domains" title="Discovery" style="color: rgb(85, 26, 139);" target="_blank">Discovery</a> documentation, or join the discussions in the <a href="http://groups.google.com/group/google-federated-login-api/web/oauth-support-in-googles-federated-login-api" title="Google Federated Login API Group" target="_blank">Google Federated Login API Group</a>, where you can ask any question and get answers from with other Identity Providers, Relying Parties and Google engineers. <br>
<br><b>The OpenID Federated Login Service is available for all Google Apps editions. However, it is disabled by default for the Premier and Education editions, and it requires the Domain Admin to manually enable it from the Control Panel. So Admins - <a title="go turn this today for your users" href="http://code.google.com/apis/apps/sso/openid_reference_implementation.html#cpanel" target="_blank">go turn this today for your users</a>. At Google.com - we already enabled it for our employees... </b><br>
</div></span></div>
</blockquote></div><br>
</div></div></blockquote></div><br>