Gholt brings up a good point in https://github.com/khussein/keystone/issues/36. In order to support the existing ecosystem of clients out there designed to work against swift and the Rackspace auth 1.0 API (as documented here http://docs.rackspacecloud.com/files/api/v1/cfdevguide_d5/content/ch03s01.html), we should make Keystone compatible with Rackspace 1.0 Auth. I therefore propose the following: 1 - we make the first release of the Keystone API be a v2.0 API (the impact is that it will be accessed with /v2/tokens instead of v1.0/tokens) docs: https://github.com/khussein/keystone/blob/master/docs/guide/src/docbkx/idmdevguide.xml. spec: https://github.com/khussein/keystone/blob/master/docs/guide/src/docbkx/idm.wadl 2 – we make Keystone respond to v1.0 requests the same way Rackspace auth does (Blueprint: https://blueprints.launchpad.net/keystone/+spec/backward-compatibility). Looking for input and feedback. Thanks, Z Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com, and delete the original message. Your cooperation is appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110517/24b097af/attachment.html>