Re: [Openstack-operators] Swift ACL's together with Keystone (v3) integration

2016-05-13 Thread Alberto Colla
2016 12:44 To: Wijngaarden, Pieter van <pieter.van.wijngaar...@philips.com> Cc: openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] Swift ACL's together with Keystone (v3) integration Hello Pieter, I did run into the same problem today. Did you find pointers to mo

Re: [Openstack-operators] Swift ACL's together with Keystone (v3) integration

2016-05-12 Thread Saverio Proto
> ‘’ only, even though that should work according to the > documentation. If you want to allow all users in another project read access > to a container, use ‘:*’ as the read-ACL. > > > > I hope this helps! > > > > With kind regards, > > Pieter van Wijngaarden

Re: [Openstack-operators] Swift ACL's together with Keystone (v3) integration

2016-05-03 Thread Wijngaarden, Pieter van
den, Pieter van <pieter.van.wijngaar...@philips.com> Cc: openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] Swift ACL's together with Keystone (v3) integration Hello Pieter, I did run into the same problem today. Did you find pointers to more updated documentation ?

Re: [Openstack-operators] Swift ACL's together with Keystone (v3) integration

2016-05-03 Thread Saverio Proto
Hello Pieter, I did run into the same problem today. Did you find pointers to more updated documentation ? Were you able to configure the cross tenant read ACL ? thank you Saverio 2016-04-20 13:48 GMT+02:00 Wijngaarden, Pieter van : > Hi all, > > I’m

[Openstack-operators] Swift ACL's together with Keystone (v3) integration

2016-04-20 Thread Wijngaarden, Pieter van
Hi all, I'm playing around with a Swift cluster (Liberty) and cannot get the Swift ACL's to work. My objective is to give users from one project (and thus Swift account?) selective access to specific containers in another project. According to