Open Stack

SSO (Single sign-on) is great. There are some problems, though:

1) If the cloud is private without Internet access, then a private SSO
service should be up and runnning
2) There is no such a thing as OpenStack ID. Should we use Launchpad?
Facebook login? Twitter?
3) Technical difficulties embedding SSO into website.

As SSO service is often located on the different domain, the browser opens
a new window, then open the SSO page there, then redirects to "our" page
that uses some cross domain messageing like postMessage to inform main page
of login results. The main page closes the popup. The stuff is rather
complex, Facebook and other social nets have SDKs that do all the stufff.

That's certainly not an easy task to make an SSO service, implement SSO SDK
and embed in into Horizon.

Anton

On Fri, Feb 6, 2015 at 11:03 PM, Tim Bell <Tim.Bell at cern.ch> wrote:

>
>
> From the sound of things, we’re not actually talking about SSO. If so, we
> would not be talking about the design of a login screen.
>
>
>
> An SSO application such as Horizon would not have a login page. If the
> user was logged in already through corporate/organisation SSO page, nothing
> would appear before the standard Horizon page.
>
>
>
> We strongly encourage our user community that if there is any web page
> asking for your credentials which is not the CERN standard SSO page, it is
> not authorised. Our SSO also supports Google/Twitter/Eduroam etc. logins.
> Some of these will be refused for OpenStack login so that having a twitter
> account alone does not get you access to CERN’s cloud resources (but this
> is an authorisation rather than authentication problem).
>
>
>
> Is there really the use case for a site where there is SSO from a
> corporate perspective but there is not a federated login SSO capability ? I
> don’t have a fundamental problem with the approach but we should position
> it with respect to the use case which is that I login in the morning and
> all applications I use (cloud and all) are able to recognise that.
>
>
>
> Tim
>
>
>
>
>
> *From:* Adam Young [mailto:ayoung at redhat.com]
> *Sent:* 06 February 2015 19:48
> *To:* openstack-dev at lists.openstack.org
> *Subject:* Re: [openstack-dev] [horizon][keystone]
>
>
>
> On 02/04/2015 03:54 PM, Thai Q Tran wrote:
>
> Hi all,
>
> I have been helping with the websso effort and wanted to get some feedback.
> Basically, users are presented with a login screen where they can select:
> credentials, default protocol, or discovery service.
> If user selects credentials, it works exactly the same way it works today.
> If user selects default protocol or discovery service, they can choose to
> be redirected to those pages.
>
> Keep in mind that this is a prototype, early feedback will be good.
> Here are the relevant patches:
> https://review.openstack.org/#/c/136177/
> https://review.openstack.org/#/c/136178/
> https://review.openstack.org/#/c/151842/
>
> I have attached the files and present them below:
>
>
>
>
> Replace the dropdown with a specific link for each protocol type:
>
> SAML and OpenID  are the only real contenders at the moment, but we will
> not likely have so many that it will clutter up the page.
>
> Thanks for doing this.
>
>
>
>
>
>
>
>
>  __________________________________________________________________________
>
> OpenStack Development Mailing List (not for usage questions)
>
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150209/bfe9a80d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12072 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150209/bfe9a80d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 10897 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150209/bfe9a80d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 10905 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150209/bfe9a80d/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 19401 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150209/bfe9a80d/attachment-0003.png>