Re: [openstack-dev] [swift][keystone] Using JSON as future ACL format

; > > > > > > *From:* Thai Q Tran [mailto:tqt...@us.ibm.com] > *Sent:* 06 June 2016 21:06 > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Subject:* [openstack-dev] [swift][keystone] Using

Re: [openstack-dev] [swift][keystone] Using JSON as future ACL format

t/overview_auth.html#tempauth From: Thai Q Tran [mailto:tqt...@us.ibm.com] Sent: 06 June 2016 21:06 To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [swift][keystone] Using JSON as future ACL format Hello all

Re: [openstack-dev] [swift][keystone] Using JSON as future ACL format

On Mon, 6 Jun 2016 13:05:46 -0700 "Thai Q Tran" wrote: > My intention is to spark discussion around this topic with the goal of > moving the Swift community toward accepting the JSON format. If would be productive if you came up with a specific proposal how to retrofit JSON

[openstack-dev] [swift][keystone] Using JSON as future ACL format

Hello all, Hope everyone had a good weekend, and hope this email does not ruin your next. We had a small internal discussion at IBM and here are some of the findings that I will present to the wider community. 1. The ":" separator that swift currently uses is not entirely safe since LDAP can