Open Stack

Everyone wants to be an OpenID provider, but nobody wants to be an
OpenID consumer.  The OpenStack development webapps have been a
refreshing exception.

If we are going to pivot the OpenStack project websites off of
consuming only the LaunchPad OpenID provider, why not allow them to
consume any arbitrary (or at least whitelisted) OpenID provider,
instead of standing up Still Yet Another provider?

One reason I like the LaunchPad ID still, is that I use Two Factor
Auth with it (you can enable the RFC standard OATH HOTP 2FA protocol
on your Launchpad/Canonical/Ubuntu account, which means it Just Works
with the Google Authenticator app), and I can use the known LaunchPad
API to get metadata about the contributors.

If we do stand up an OpenStack.org identity provider, will it also
support such an API, and support 2FA, and the various new identity and
metadata APIs that have been and are being published?

..m


On Tue, Sep 24, 2013 at 11:43 AM, Stefano Maffulli
<stefano at openstack.org> wrote:
> hello folks
>
> at the Foundation we've started a new project to provide OpenID to our
> systems. One of the first tasks is to collect the full list of sites
> that nowadays depend on Launchpad ID. Can you please help me complete
> the list below?
>
> 1) review.openstack.org
> 2) summit.openstack.org
> 3) wiki.openstack.org
> 4) ask.openstack.org (but can accept other OpenID providers and Oauth)
> ...
> y) groups.openstack.org (under development)
> x) launchpad.net (bugs and blueprints)
>
> Thanks,
> Stef
>
> --
> Ask and answer questions on https://ask.openstack.org
>
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra