Bug 1041850

Summary:	[RFE][python-keystoneclient]: Move auth system fom novaclient to keystoneclient
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/python-keystoneclient/+spec/keystoneclient-auth-system
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_superseded
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:27:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 19:42:13 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/python-keystoneclient/+spec/keystoneclient-auth-system.

Description:

Historically we had auth_system in novaclient used for Rackspace Cloud key based auth system but now used for other things :

We are using it for X.509 auth, where we need to authenticate against
the HTTP server where keystone is running with the user certificate
instead of using the passwordCredentials dict. Basic or Digest auth are
other use cases for this system.

We should move that feature from novaclient to keystone if we ever want to finally move novaclient to keystoneclient.

Specification URL (additional information):

None