On 08/07/2013 08:16 AM, Tim Bell wrote:
Yes, this is something we're very interested in. Joe's blueprint
(https://blueprints.launchpad.net/keystone/+spec/virtual-idp) has a number of
the user stories and would be a good place to start to add others.
Work is underway under two approaches.
1. is the OAuth Support. It is in the final stages, and should merge
by H3.
2. is the U of Kent Federaion blueprint, which is also well underway,
and will have pieces of it in by H3 as well\\\
The split of Identity from Assignments was essential to a consistant
approach here. Henry Nash is taking this to the next with the ability
to have multiple LDAP IdP, one per domain.
There are three pieces to keep clear.
1. Mechanism for Identity Attribute delivery. SQL and LDAP are "pull
mechanisms" where as SAML etc are push. The end result is the same,
though: we have some data that we can trust to use as the basis of
authorization decisions.
2. Mapping. This is the focus of the current Kent work. We need a way
to get the attributes, whatever they are, into a format that Keystone
understands.
3. Assignments. These are owned by Keystone. This consumes the
mapping in order to actually give the token the attributes.
In addition, we need rules for registering domains. Currently, each
domain is limited to one mechanism. For example, a domain cannot do
both LDAP and SQL. If a given domain will use SAML, it will be limited
to only SAML. I suspect that this limitation will be acceptable for the
near future. Please let me know if this is not the case.
Tim
From: Brad Topol [mailto:bto...@us.ibm.com]
Sent: 07 August 2013 13:55
To: Joe Savak
Cc: Miller, Mark M (EB SW Cloud - R&D - Corvallis);
openstack@lists.openstack.org; Rok Kralj; Tim Bell; Dolph Mathews
Subject: Re: [Openstack] Openstack login via SimpleSamlPHP (LDAP, OAuth,
OpenID, etc..)
Joe, Tim,
I am seeing a strong interest in keystone federated identity support from
customers. I was planning on submitting a keystone design summit session
proposal on this topic where we could discuss the use cases and requirements
that customers are bringing forward and make sure we get all the bases covered.
Sounds like you are seeing interest in this as well.
Thanks,
Brad
Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet: bto...@us.ibm.com
Assistant: Cindy Willman (919) 268-5296
From: Joe Savak <joe.sa...@rackspace.com>
To: Tim Bell <tim.b...@cern.ch>, "Miller, Mark M (EB SW Cloud - R&D - Corvallis)"
<mark.m.mil...@hp.com>, Rok Kralj <o...@rok-kralj.net>, "openstack@lists.openstack.org"
<openstack@lists.openstack.org>
Date: 08/06/2013 04:06 PM
Subject: Re: [Openstack] Openstack login via SimpleSamlPHP (LDAP, OAuth,
OpenID, etc..)
________________________________________
If we allow Keystone to handle the identity federation (both with an incoming
SAML to token exchange and an outgoing token to SAML exchange), then wouldn't
both GUI and CLI SSO be possible?
See here for more information:
https://blueprints.launchpad.net/keystone/+spec/virtual-idp
And a pretty picture:
https://wiki.openstack.org/wiki/File:Virtual_Identity_Providers.png
Rok -- thank you for starting this. I do think your GUI-SSO solution has benefits regardless of the language it uses.
From: Tim Bell [mailto:tim.b...@cern.ch]
Sent: Tuesday, August 06, 2013 1:05 PM
To: Miller, Mark M (EB SW Cloud - R&D - Corvallis); Rok Kralj;
openstack@lists.openstack.org
Subject: Re: [Openstack] Openstack login via SimpleSamlPHP (LDAP, OAuth,
OpenID, etc..)
I would be very interested in a native SAML for single sign on implementation with Horizon login. This would mean Python rather than PHP along with potentially (I think) creating a situation where a user can use the Web GUI through single sign on but not able to use CLI.
Depending on the use cases, this may not be an issue but as far as I understand, it is a limitation of the technology at present.
Tim
From: Miller, Mark M (EB SW Cloud - R&D - Corvallis) [mailto:mark.m.mil...@hp.com]
Sent: 06 August 2013 19:06
To: Rok Kralj; openstack@lists.openstack.org
Subject: Re: [Openstack] Openstack login via SimpleSamlPHP (LDAP, OAuth,
OpenID, etc..)
How is this different than the new H-2 split backend functionality?
From: Rok Kralj [mailto:o...@rok-kralj.net]
Sent: Tuesday, August 06, 2013 5:38 AM
To: openstack@lists.openstack.org
Subject: [Openstack] Openstack login via SimpleSamlPHP (LDAP, OAuth, OpenID,
etc..)
As far as I know, the ability to log in to OpenStack via arbitrary Identity Provider (IdP) is a widely desired feature. Therefore, we have decided to integrate Keystone & Horizon with Simple Saml PHP, since it provides a lot of AUTH sources (aka. IdPs), for example LDAP, database, facebook, etc... Check out our effort in this short video (40s):
http://www.youtube.com/watch?v=qmJAumoh4U8
For more, the instructions and a short introduction is available in the attached readme.pdf.
Feedback is really appreciated._______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
