Difference between revisions of "Swift/ideas/swiftclient-keystone-session"
Jjw-sohonet (talk | contribs) (Start adding detail) |
Jjw-sohonet (talk | contribs) (Add past patch links) |
||
| Line 9: | Line 9: | ||
== Past Related Patches == | == Past Related Patches == | ||
| − | * Use generic keystone client instead of versioned one (Abandoned) | + | * Use generic keystone client instead of versioned one [https://review.openstack.org/443104] (Abandoned) |
| − | * WIP: Use keystone session when possible | + | * WIP: Use keystone session when possible [https://review.openstack.org/456205] |
| − | * Adding session to switfclient. (Abandoned) | + | * Adding session to switfclient [https://review.openstack.org/270045] (Abandoned) |
| − | * Add v1password keystoneauth plugin (Merged) | + | * Add v1password keystoneauth plugin [https://review.openstack.org/300697] (Merged) |
| − | * Adding keystoneauth sessions support (Merged) | + | * Adding keystoneauth sessions support [https://review.openstack.org/298968] (Merged) |
Revision as of 14:11, 3 May 2017
Swiftclient Keystone Session Support
Some work has been done in the past on a very lightweight method to allow the python-swiftclient to make use of Keystone sessions whilst maintaining the existing API. However, more recent updates to Keystone, and the deprecation of version specific sessions mean that we may need to explore supporting Keystone sessions more thoroughly.
Current Patch and Related Discussion
Patch "Use keystone session when possible" [1] has been added by jaosorior as an indication of what changes would be required within python-swiftclient to properly support generic Keystone sessions and Keystone version detection.
