On 27 May 2014 13:42, Lukasz Oles <loles at mirantis.com> wrote: > Hello fuelers, > > we(I and Kamil) would like start discussion about "Enforce access control > for Fuel UI" blueprint > https://blueprints.launchpad.net/fuel/+spec/access-control-master-node. > > First question to David, as he proposed this bp. Do you want to add more > requirements? > > To all. What do you think about using keystone as authorization tool? We > described all pros/cons in the specification. > I would suggest both an internal authentication database and the option of plugging additional options in, with keystone being one of them and perhaps something like oauth being another. Keystone may not be available at the time of the build, or accessible from the network that's used for the initial build. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/957209da/attachment.html>