I had the same thought :)

Config option or some documentation that outlines changes in policy.json.

Either way, we should support both.

David Chadwick <d.w.chadw...@kent.ac.uk> wrote on 09/17/2014 10:07:43 AM:

> From: David Chadwick <d.w.chadw...@kent.ac.uk>

> To: openstack-dev@lists.openstack.org,
> Date: 09/17/2014 10:10 AM
> Subject: Re: [openstack-dev] [Keystone][Horizon] CORS and Federation
>
>
>
> On 17/09/2014 14:55, Marek Denis wrote:
> >
> >
> > On 17.09.2014 15:45, Steve Martinelli wrote:
> >> ++ to your suggestion David, I think making the list of trusted IdPs
> >> publicly available makes sense.
> >
> > I think this might be useful in an academic/science world but on the
> > other hand most cloud providers from the 'business' world might be very
> > reluctant to expose list of their clients for free.
> >
>
> It is interesting that this latter comment came from the
> academic/science world, whereas the supportive one came from the
> business world :-)
>
> So maybe there could be a config parameter in keystone to determine
> which option is installed?
>
> regards
>
> David
>
> >
> > cheers,
> >
> > Marek.
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> >
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to