This isn't something I've tested myself, but you should be able to get a v3 token for a user and project in the default domain and have the keystoneclient middleware validate the token either offline or against the v2.0 API. What's the issue you're running into? -Dolph On Wed, May 1, 2013 at 1:29 PM, Adrian Smith <adrian_f_smith at dell.com>wrote: > Assuming a user has retrieved a token from Keystone using the v3 API > can that token be consumed by Swift? > > Looking at the auth_token [1] middleware I presume it can but I'm > having trouble testing it in my environment. > > Are there any restrictions or gotchas to be aware of when using Swift > ACLs with Keystone v3? > > Thanks > Adrian > > [1] > https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130501/e3e5992a/attachment.html>