[OpenID] [LIKELY_SPAM]Re: Google OpenID IDP is now live

Wed Oct 29 19:25:52 UTC 2008

>> I hope I'm misunderstanding what you are saying and that you support the
standard.
>> That's the hub and spoke model, pretending to be an open system.Hopefully
my follow on post clarified Dick & Peter's questions.

In fact, one of the questions I raised at the UX
summit<http://sites.google.com/site/oauthgoog/UXFedLogin/09nov-uxsummit>last
week was how an E-mail outsourcing services like our
GoogleAppsForYourDomain could offer this type of OpenID IDP as a service to
those domains.  Since we host thousands of such domains, the auto-discovery
aspects of OpenID are key.  However the challenge we face is how to avoid
lock-in.  In particular, we need a way for an enterprise/ISP/school/etc. to
start using our IDP, but later move it somewhere else without breaking
federated login for their users.  Similarly, they should be able to run
their own and then migrate it to us.  OpenID provides a great set of
abstraction layers to make this possible, however there is still a lot more
research we need to do into the actual mechanics of getting that to work.

On Wed, Oct 29, 2008 at 11:39 AM, Peter Williams <pwilliams at rapattoni.com>wrote:

> That's not openid.
>
> That's the hub and spoke model, pretending to be an open system.
>
> Openid will go the way of saml if one stays with this way of thinking (core
> rp code must know how to interact with particular idps, just for basic
> websso.)
>
> -----Original Message-----
> From: Breno de Medeiros <breno at google.com>
> Sent: Wednesday, October 29, 2008 2:08 PM
> To: Dick Hardt <dick.hardt at gmail.com>
> Cc: Joseph Smarr <joseph at plaxo.com>; OpenID List <general at openid.net>
> Subject: [LIKELY_SPAM]Re: [OpenID] Google OpenID IDP is now live
>
>
> Our API documentation explains what we recommend RPs to implement to
> facilitate users attempts to login using Google. (Effectively you can
> hook up your button or user a parser for email addresses and perform
> discovery at the endpoint above for gmail). Due to the patchy library
> support of EAUT at present, we think this is an adequate interim
> solution, and the modifications that we suggest RPs to perform are
> independent of the actual discovery mechanism supported.
>
>
> On Wed, Oct 29, 2008 at 10:53 AM, Dick Hardt <dick.hardt at gmail.com> wrote:
> > "www.google.com/accounts/o8/id"?
> >
> > gosh, I'll remember that one! :-)
> >
> > Given the non memorable openid generated by Google, I'd be interested in
> how
> > Google thinks users will login with their OpenID if they can't type in
> > gmail.com or google.com -- these should work. Will they?
> >
> > -- Dick
> >
> > On 29-Oct-08, at 10:38 AM, Breno de Medeiros wrote:
> >
> >> At this point, you can discover using www.google.com/accounts/o8/id as
> >> your OP identifier if you so wish. However, initially we will require
> >> registration. Thanks.
> >>
> >> On Wed, Oct 29, 2008 at 10:30 AM, Andrew Arnott <andrewarnott at gmail.com
> >
> >> wrote:
> >>>
> >>> Forgive my apparent ignorance, but this doesn't look like a standard
> >>> OpenID
> >>> Provider.  I just tried to log into my own RP typing in "google.com"
> to
> >>> use
> >>> directed identity, since I have no idea what my own identifier URL
> would
> >>> be,
> >>> and no endpoints were found.  Also tried "gmail.com".
> >>> When I read the blog, it mentioned OpenID but the link was to register
> >>> for
> >>> federated login.  I thought Shibboleth was about federated login and
> >>> OpenID
> >>> was about letting any RP log into an IDP.  Why does an RP have to
> >>> register
> >>> with Google before using its IDP?  And even if it registered, that
> can't
> >>> automatically make "google.com" discoverable, so this doesn't feel
> like
> >>> OpenID at all to me.
> >>>
> >>> Unhappy, but hoping someone can explain it to me.
> >>> On Wed, Oct 29, 2008 at 9:02 AM, Eric Sachs <esachs at google.com> wrote:
> >>>>
> >>>> Google's IDP is now live.  You can try it on Plaxo, ZoHo, & Buxfer and
> >>>> hopefully more RPs to come soon.  Here is the blog post with more
> >>>> details,
> >>>> including information on how RPs can sign up to use the service:
> >>>>
> >>>>
> >>>>
> >>>>
> http://google-code-updates.blogspot.com/2008/10/google-moves-towards-single-sign-on.html
> >>>>
> >>>> And yes, it does allow RPs to request a user's E-mail address via AX
> as
> >>>> an
> >>>> option.  I'll let Joseph Smarr from Plaxo respond with details on how
> >>>> they
> >>>> are using that feature to further simplify the signup flow for Plaxo.
> >>>> Eric Sachs
> >>>> Product Manager, Google Security
> >>>> _______________________________________________
> >>>> general mailing list
> >>>> general at openid.net
> >>>> http://openid.net/mailman/listinfo/general
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> general mailing list
> >>> general at openid.net
> >>> http://openid.net/mailman/listinfo/general
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> --Breno
> >>
> >> +1 (650) 214-1007 desk
> >> +1 (408) 212-0135 (Grand Central)
> >> MTV-41-3 : 383-A
> >> PST (GMT-8) / PDT(GMT-7)
> >> _______________________________________________
> >> general mailing list
> >> general at openid.net
> >> http://openid.net/mailman/listinfo/general
> >
> >
>
>
>
> --
> --Breno
>
> +1 (650) 214-1007 desk
> +1 (408) 212-0135 (Grand Central)
> MTV-41-3 : 383-A
> PST (GMT-8) / PDT(GMT-7)
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openid.net/pipermail/general/attachments/20081029/12afde82/attachment.htm 